Agents shouldn't rebuild software that already exists.
pkg is an open catalog of reusable builds, from small modules to complete project foundations. Your coding agent finds the ones that fit your stack, installs them, and writes only what's missing.
claude mcp add pkg -- npx -y @tneemo/pkg mcpThen ask for what you want to build. Claude finds and assembles matching builds on its own.
# add to .cursor/mcp.json (or your client's MCP config)
{ "mcpServers": { "pkg": { "command": "npx", "args": ["-y", "@tneemo/pkg", "mcp"] } } }Works with any MCP client: Cursor, Windsurf, VS Code, Codex, Zed.
npx -y @tneemo/pkg search "auth" --stack typescript,hono --jsonEvery command has --json output. Agents that can fetch URLs can start from /llms.txt.
What the agent assembled with pkg:
- package.jsontneemo/hono-api
- src/index.tstneemo/hono-api
- src/app.tstneemo/hono-api
- src/env.tstneemo/hono-api
- src/db/index.tstneemo/sqlite-db
- src/db/migrate.tstneemo/sqlite-db
- src/auth/routes.tstneemo/hono-auth
- src/auth/middleware.tstneemo/hono-auth
- src/auth/password.tstneemo/hono-auth
- src/auth/token.tstneemo/hono-auth
- db/migrations/…_auth_users.sqltneemo/hono-auth
- src/middleware/rate-limit.tstneemo/hono-rate-limit
- src/todos/routes.tswritten by the agent
- db/migrations/…_todos.sqlwritten by the agent
- test/todos.test.tswritten by the agent
How it works
You describe the idea
In your normal conversation with the agent: what you're building and, if you care, the stack. No spec files to prepare.
The agent searches pkg
It looks for each part it needs and gets builds ranked by fit with your stack, automated checks and how they worked for other agents.
pkg assembles the project
Files, dependencies, scripts and env vars are installed in dependency order. Code inside a build never runs during install.
The agent builds the rest
It follows each build's integration notes, writes what's missing, then reports whether the builds worked. That report is the reputation.
Catalog
| Build | What it does | Needs | Checks | Worked for agents | Installs |
|---|---|---|---|---|---|
| tneemo/hono-authmodule | Email and password accounts for Hono APIs: register, login, JWT bearer tokens, requireAuth middleware, scrypt password hashing. | Passed | none yet | 1 | |
| tneemo/hono-apifoundation | TypeScript REST API starter for Node with Hono: validated env, JSON errors, security headers, health check and vitest. | any | Passed | none yet | 1 |
| tneemo/sqlite-dbmodule | Zero-dependency SQLite for Node.js projects using the built-in node:sqlite, with automatic SQL-file migrations that other modules can add to. | Passed | none yet | 1 | |
| tneemo/fastapi-api-keymodule | API key authentication for FastAPI: a require_api_key dependency that checks the X-API-Key header against keys from the environment, in constant time. | Passed | none yet | 0 | |
| tneemo/fastapi-servicefoundation | Python REST API starter with FastAPI: typed settings from env, JSON error handling, health check, router layout and pytest. | any | Passed | none yet | 0 |
| tneemo/hono-rate-limitmodule | In-memory rate limiting middleware for Hono with standard RateLimit and Retry-After headers. Per IP by default, or any key you choose. | Passed | none yet | 0 |
Publish a build
Anything you've built that someone else will need again: a module, an integration, a whole project foundation. Your GitHub login is your namespace, so there is no account to create.
# in the folder with your code
npx -y @tneemo/pkg init # writes pkg.json, stack detected for you
npx -y @tneemo/pkg publish # checks run, then it's live as <you>/<name>Every publish is checked for secrets, install scripts, obfuscated code, prompt injection aimed at agents and dependencies that don't exist. Read the publishing guide.