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/initgit 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/init)<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/init"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/init.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.00012 | $0.00583 |
| Opus 5 | $0.00006 | $0.00292 |
| Sonnet 5 | $0.00002 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
init 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
INITIALIZATION MODE ACTIVATED
You are now in INIT (initialization) phase.
Purpose
Initialize a new task by analyzing the project and determining the appropriate workflow.
Your Tasks
-
Analyze the Project
- Scan project structure
- Identify tech stack and patterns
- Note existing conventions
- Check for existing context files (
tmp/prd.md,tmp/design.md,tmp/project-brief.md,tmp/tasks.md,tmp/active-context.md)
-
Understand the Request
- What is the user asking for?
- What is the scope?
- Are there ambiguities to clarify?
-
Determine Complexity Level
Level Type Characteristics Workflow 1 Quick Fix Single file, obvious change, < 30 min /build->/review2 Simple Task Few files, clear scope, < 2 hours /plan->/qa->/build->/review3 Feature Multiple files, design decisions needed /plan->/creative->/qa->/build->/review4 Complex Architectural, cross-cutting, multi-day /plan->/creative->/qa->/build->/review->/archive -
Set Up Context
- Create/update
tmp/tasks.mdif needed - Create/update
tmp/active-context.mdif needed - Note any existing progress
- Create/update
-
Route to Next Command
- Level 1: Recommend
/build - Level 2-4: Recommend
/plan
- Level 1: Recommend
Output Format
## Task Initialization
### Project Analysis
- **Tech Stack:** [languages, frameworks]
- **Structure:** [monorepo, single app, etc.]
- **Conventions:** [patterns observed]
### Request Understanding
- **Task:** [what user wants]
- **Scope:** [files/modules affected]
- **Ambiguities:** [questions if any]
### Complexity Assessment
**Level: [1-4]**
**Reasoning:**
- [Why this level]
- [Key factors]
### Recommended Workflow
[workflow path, e.g., /plan -> /creative -> /qa -> /build -> /review]
### Next Step
Run `/plan` to begin planning (or `/build` for Level 1 tasks).
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 · 81 lines · 12 tokens per session scan A 72e24c2717b2
init is a command published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 583 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
git
Git operations with intelligent commit messages and workflow optimization.
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.