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/d-padmanabhan/agent-engineering-handbook/buildgit clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbookWrote 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/d-padmanabhan/agent-engineering-handbook/build)<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/build"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/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 | $0.00010 | $0.00374 |
| Opus 5 | $0.00005 | $0.00187 |
| Sonnet 5 | $0.00002 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00037 |
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 5d 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.
What it actually says
BUILD MODE ACTIVATED
You are now in IMPLEMENTATION phase.
Prerequisites
Before building, confirm:
- Plan has been approved by user (HITL / human-in-the-loop)
- QA validation passed (for Level 2+ tasks)
- Creative phase completed (for Level 3-4 tasks)
If no plan exists, suggest running /plan first.
Your Tasks
-
Follow the Approved Plan
- Implement exactly what was discussed
- Don't add unplanned features
- Don't refactor unrelated code
-
Make Incremental Changes
- Small, testable commits
- One logical change at a time
- Update context files as you progress
-
Apply Standards
- Follow coding standards from rules (100-core.mdc, language-specific rules)
- Include error handling
- Add appropriate logging
- Consider security implications
-
Stop at Boundaries
- Complete the agreed scope, then STOP
- Don't fix unrelated issues
- Don't optimize prematurely
- Note improvements for future work
Constraints
- Implement ONLY what was planned
- Include error handling and logging
- Follow existing code patterns/conventions
- No TODO comments - complete the implementation
- No placeholders or incomplete sections
If You Encounter Issues
- Trivial fixes (typos, obvious bugs): Fix immediately
- Substantial changes needed: STOP, document the issue, discuss before proceeding
When Done
Say: "Implementation complete. Ready for /review when you are."
Summarize:
- What was implemented
- Any deviations from plan (and why)
- Files changed
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.
- 5d ago First seen · 65 lines · 10 tokens per session scan A dcb7ae259875
build is a command published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 5d ago), licensed MIT. It adds 10 tokens to every session and 374 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.