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/florianbruniaux/claude-code-plugins/plan-validategit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/plan-validate)<a href="https://agentmods.dev/commands/florianbruniaux/claude-code-plugins/plan-validate"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-plugins/plan-validate.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.00037 | $0.01554 |
| Opus 5 | $0.00018 | $0.00777 |
| Sonnet 5 | $0.00007 | $0.00311 |
| Haiku 4.5 | $0.00004 | $0.00155 |
Grade A, and why
plan-validate 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 yesterday.
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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Validate — 2-Layer Validation
Independently validate the plan produced by /plan-start. No code is written. Run /clear after this command before running /plan-execute.
Validation is separate from planning by design: validators that didn't write the plan are not anchored to its assumptions.
Prerequisite
A committed plan file must exist at docs/plans/plan-{name}.md. If multiple plans exist, list them and ask the user which to validate.
Layer 1: Structural Validation
Run immediately, no agents required. Check the plan document for:
Format & Completeness
- All required sections present (Summary, Decisions, Architecture, Tasks, Test Plan, Out of Scope)
- Each task has: description, files affected, acceptance criteria, layer assignment
Dependency Chain
- No circular dependencies between tasks
- Tasks in higher layers only depend on tasks in lower layers
- All stated dependencies exist in the plan
File Existence
- Every file listed for modification actually exists in the codebase (use Glob)
- New files are in appropriate directories per project conventions
ADR Consistency
- Plan decisions align with ADRs created during
/plan-start - No contradiction with existing ADRs in
docs/adr/
CLAUDE.md Compliance
- Plan respects all hard rules in CLAUDE.md
- No first principles violations (no workarounds, no backward-compat shims)
Test Coverage
- Every new function/component has a corresponding test task
- TDD-marked tasks have failing test written before implementation task
Record all Layer 1 issues with severity (BLOCKER / WARNING / INFO) before proceeding to Layer 2.
Layer 2: Specialist Review
Select agents by applying trigger rules to the plan content. No user input needed — triggers are objective.
Validation agent pool:
| Agent | Trigger | Model |
|---|---|---|
security-reviewer |
Auth, payments, PII, RBAC, new public APIs | Opus |
db-migration-reviewer |
New tables, columns, indexes, or migration files | Opus |
performance-reviewer |
New queries, resolvers, routes, or added dependencies | Sonnet |
design-system-reviewer |
New UI components or visual styling changes | Sonnet |
ux-reviewer |
New pages, forms, modals, or interaction patterns | Sonnet |
cross-platform-reviewer |
Changes touching both web and mobile, or shared packages | Sonnet |
native-app-reviewer |
Mobile screens, native UI package changes | Sonnet |
integration-reviewer |
New external services, libraries, or OTEL config | Opus |
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.
- yesterday First seen · 188 lines · 37 tokens per session scan A 62789cfbed2e
plan-validate is a command published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 1,554 once invoked, about $0.0002 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-09-04.
Other commands, from other repositories
aso
App Store Optimization command. iOS app listing analysis via the iTunes API, keyword optimization, and competitor comparison.
content-generate
Social media content generation command. Produces ready-to-use posts, captions, visual briefs, and hashtags for the given platform and type.
api-doc
API documentation generation. Scans route definitions and produces structured API docs.
audit
Quality audit command. Runs a systematic audit over code, structure, or process.
brief
Project briefing command. Turns raw project ideas into structured, actionable briefs.
changelog
Automatic changelog generation. Produces a structured changelog from commit history.