Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-cli/main/.claude/commands/build.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-cliWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/namastexlabs/automagik-cli/build)<a href="https://agentmods.dev/commands/namastexlabs/automagik-cli/build"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-cli/build.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00000 | $0.01553 |
| Opus 5 | $0.00000 | $0.00776 |
| Sonnet 5 | $0.00000 | $0.00311 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
build 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 3d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build
allowed-tools: Task(), Read(), Write(), Edit(), MultiEdit(), Bash(), Glob(), Grep(), mcp__gemini__, mcp__search-repo-docs__, mcp__ask-repo-agent__, mcp__genie_memory__, mcp__send_whatsapp_message__, mcp__wait__ description: Implement features, write code, and build functionality
Build and implement features, write code, and create functionality from requirements.
Auto-Loaded Project Context:
@/CLAUDE.md @/docs/ai-context/project-structure.md @/docs/ai-context/docs-overview.md
Usage
# Implement new features
/build "Add user authentication system"
/build "Create payment processing API"
/build "Implement real-time notifications"
# Code specific functionality
/build "Write function to validate email addresses"
/build "Create database migration for user table"
/build "Build REST endpoints for product catalog"
Intelligent Implementation Strategy
Step 1: Requirement Analysis
Parse user request: "$ARGUMENTS"
Implementation Categories:
- Simple Function/Util → Direct implementation
- API/Endpoint → Pattern-based implementation
- Feature/Component → Multi-agent analysis
- System Integration → Comprehensive analysis
Step 2: Progressive Enhancement Strategy
Level 1: Direct Implementation (Simple tasks)
- Single file implementations
- Follow existing patterns
- Minimal dependencies
Level 2: Pattern Analysis (Moderate complexity)
- Analyze existing similar implementations
- Use 1-2 sub-agents for guidance
- Follow established conventions
Level 3: Multi-Agent Design (Complex features)
- Deploy 2-4 specialized sub-agents:
- Architecture_Analyst: Design approach using project patterns
- Implementation_Specialist: Code structure and organization
- Integration_Expert: Dependencies and connections
- Quality_Validator: Security, performance, testing
Level 4: Expert Consultation (High complexity)
- Use Gemini consultation for complex technical decisions
- Repository pattern research via search-repo-docs
- Cross-reference best practices
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.
- 3d ago First seen · 221 lines · 0 tokens per session scan A 02cbfe081bde
build is a command published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,553 tokens. 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-09-04.
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.