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/validate_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/validate_plan)<a href="https://agentmods.dev/commands/spideynolove/claude-dotfiles/validate_plan"><img src="https://agentmods.dev/badge/commands/spideynolove/claude-dotfiles/validate_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.00015 | $0.00474 |
| Opus 5 | $0.00008 | $0.00237 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
validate_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 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
Validate Plan
You are tasked with validating that an implementation plan was correctly executed. Run all automated success criteria, identify deviations, and list what still needs manual verification.
Setup
When invoked:
- Locate the plan (use path if provided; otherwise check recent commits or ask)
- Gather implementation evidence:
git log --oneline -n 20 git diff HEAD~N..HEAD # cover implementation commits - Read the plan completely
Validation Process
Step 1: Discover What Was Done
Spawn parallel research agents to verify:
- Which files were changed vs what the plan specified
- Whether tests were added/updated as specified
- Whether automated criteria commands actually pass
Step 2: Systematic Check Per Phase
For each phase:
- Check completion status — look for
- [x]checkmarks - Run every command from "Automated Verification"
- Document pass/fail
- Think about edge cases: error handling, regressions, missing validations
Step 3: Generate Validation Report
## Validation Report: [Plan Name]
### Implementation Status
✓ Phase 1: [Name] — Fully implemented
✓ Phase 2: [Name] — Fully implemented
⚠️ Phase 3: [Name] — Partially implemented
### Automated Verification Results
✓ [command] — passed
✗ [command] — failed: [reason]
### Code Review Findings
#### Matches Plan:
- [Finding: file:line]
#### Deviations from Plan:
- [Deviation: file:line] ([improvement or concern])
#### Potential Issues:
- [Risk or missing piece]
### Manual Testing Required:
- [ ] [Step the human must verify]
- [ ] [Another step]
### Recommendations:
- [Action before merge]
Guidelines
- Run ALL automated checks — don't skip
- Be honest about shortcuts or incomplete items from this session
- Think critically: does the implementation actually solve the problem?
- Consider maintainability, not just correctness
Recommended Workflow
/create_plan → /implement_plan → /validate_plan → commit → PR
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 · 82 lines · 15 tokens per session scan A a108246408cd
validate_plan is a command published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 474 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
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.