Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/madappgang/claude-code/setup-projectgit clone --depth 1 https://github.com/MadAppGang/claude-codeWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00029 | $0.03722 |
| Opus 5 | $0.00015 | $0.01861 |
| Sonnet 5 | $0.00006 | $0.00744 |
| Haiku 4.5 | $0.00003 | $0.00372 |
Grade A, and why
setup-project scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 582 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Set up a production-ready Bun + TypeScript backend project from scratch with all necessary tooling, configuration, and project structure. This creates a solid foundation following industry best practices.
Project Setup Request
$ARGUMENTS
Workflow
STEP 0: Initialize Todo List (MANDATORY FIRST STEP)
Create a todo list to track the setup process:
TaskCreate with the following items:
- content: "Gather project requirements and configuration preferences"
status: "in_progress"
activeForm: "Gathering project requirements"
- content: "Initialize Bun project and install dependencies"
status: "pending"
activeForm: "Initializing Bun project"
- content: "Configure TypeScript (strict mode)"
status: "pending"
activeForm: "Configuring TypeScript"
- content: "Configure Biome (formatter + linter)"
status: "pending"
activeForm: "Configuring Biome"
- content: "Set up Prisma with PostgreSQL"
status: "pending"
activeForm: "Setting up Prisma"
- content: "Create project structure (folders)"
status: "pending"
activeForm: "Creating project structure"
- content: "Create core utilities (errors, logger, config)"
status: "pending"
activeForm: "Creating core utilities"
- content: "Set up Hono app and server"
status: "pending"
activeForm: "Setting up Hono app"
- content: "Create middleware (error handler, logging, validation)"
status: "pending"
activeForm: "Creating middleware"
- content: "Set up environment variables and configuration"
status: "pending"
activeForm: "Setting up environment configuration"
- content: "Create Docker configuration"
status: "pending"
activeForm: "Creating Docker configuration"
- content: "Set up testing infrastructure"
status: "pending"
activeForm: "Setting up testing"
- content: "Create package.json scripts"
status: "pending"
activeForm: "Creating npm scripts"
- content: "Create .gitignore and other config files"
status: "pending"
activeForm: "Creating config files"
- content: "Create README.md with project documentation"
status: "pending"
activeForm: "Creating README"
- content: "Initialize git repository"
status: "pending"
activeForm: "Initializing git"
- content: "Run initial quality checks"
status: "pending"
activeForm: "Running quality checks"
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 582 lines · 29 tokens per session scan A 7aff9d44e6c2
setup-project is a command published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 3,722 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.