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/plangit 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/plan)<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/plan"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/plan.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.00013 | $0.00418 |
| Opus 5 | $0.00006 | $0.00209 |
| Sonnet 5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
plan 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 6d 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
PLANNING MODE ACTIVATED
You are now in PLANNING phase. Do NOT write code yet.
Your Tasks
-
Analyze the Request
- Understand scope, constraints, and requirements
- Identify what's essential vs nice-to-have
- Note any ambiguities
-
Check Existing Code
- Look for patterns, conventions, and reusable components
- Understand the current architecture
- Identify files/modules that will be affected
-
Design the Solution
- Propose approach with rationale
- Consider 2-3 alternatives with pros/cons
- Identify dependencies and risks
- Plan testing strategy
-
Document the Plan
- Update
tasks.mdoractive-context.mdif they exist - List files to be modified
- Outline implementation steps
- Update
-
Present and WAIT
- Show the plan clearly
- Ask for explicit approval before proceeding (HITL / human-in-the-loop)
- Answer any clarifying questions
Output Format
## Plan: [Brief Title]
### Problem
[What we're solving]
### Proposed Solution
[Your approach]
### Alternatives Considered
1. [Alternative 1] - [Why not chosen]
2. [Alternative 2] - [Why not chosen]
### Files Affected
- `path/to/file1.py` - [What changes]
- `path/to/file2.py` - [What changes]
### Implementation Steps
1. [Step 1]
2. [Step 2]
3. [Step 3]
### Risks
- [Risk 1]
- [Risk 2]
### Testing Strategy
- [How to test]
Rules
- Ask max 3 clarifying questions if scope is ambiguous
- Do NOT start coding until user approves
- Keep plans concise but complete
- Consider security implications
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.
- 6d ago First seen · 75 lines · 13 tokens per session scan A ca32e9a59733
plan is a command published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 418 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.