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/spideynolove/claude-dotfiles/implement_plangit clone --depth 1 https://github.com/spideynolove/claude-dotfilesWrote 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/spideynolove/claude-dotfiles/implement_plan)<a href="https://agentmods.dev/commands/spideynolove/claude-dotfiles/implement_plan"><img src="https://agentmods.dev/badge/commands/spideynolove/claude-dotfiles/implement_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 | $0.00013 | $0.00482 |
| Opus 5 | $0.00006 | $0.00241 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
implement_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 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Plan
You are tasked with implementing an approved plan. Execute phase-by-phase, track progress in the plan file itself, and pause for human verification after each phase's automated checks pass.
Getting Started
If given a plan path:
- Read the plan completely, note existing checkmarks (
- [x]) - Read all files mentioned in the plan FULLY
- Create a TodoWrite list mirroring the plan phases
- Start from the first unchecked item
If no plan path provided, ask for one.
Implementation Philosophy
Plans are carefully designed, but reality is messy. Your job:
- Follow the plan's intent, not just its words
- Implement each phase fully before moving to the next
- Update checkboxes in the plan file as sections complete
- Keep the end goal in mind; maintain forward momentum
When reality diverges from the plan, STOP and report:
Issue in Phase [N]:
Expected: [what the plan says]
Found: [actual situation]
Why this matters: [explanation]
How should I proceed?
Verification Approach
After implementing each phase:
- Run all automated success criteria from the plan
- Fix any failures before proceeding
- Check off completed items in the plan file with Edit
- Pause with this message:
Phase [N] Complete — Ready for Manual Verification
Automated checks passed:
- [check: command]
- [check: command]
Please perform manual verification:
- [ ] [Manual step from plan]
- [ ] [Manual step from plan]
Let me know when done so I can proceed to Phase [N+1].
Do NOT check off manual items until the user confirms them.
If instructed to run multiple phases consecutively, skip the pause between phases — only pause at the final phase.
If Stuck
- Re-read the relevant code before asking
- Consider if the codebase has evolved since the plan was written
- Present the mismatch clearly and ask for guidance
- Use sub-agents only for targeted exploration of unfamiliar code
Resuming
If the plan has existing checkmarks:
- Trust that completed work is done
- Start from the first unchecked item
- Verify previous work only if something seems off
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 · 76 lines · 13 tokens per session scan A 55e82fcef5f1
implement_plan is a command published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 482 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-31.
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.