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 skills add FlorianBruniaux/claude-code-plugins --skill plan-pipeline-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/skills/florianbruniaux/claude-code-plugins/plan-pipeline-validate)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/plan-pipeline-validate"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/plan-pipeline-validate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/plan-pipeline-validate"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/plan-pipeline-validate.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.01591 |
| Opus 5.5 | $0.00016 | $0.00636 |
| Sonnet 5.5 | $0.00008 | $0.00318 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
plan-pipeline-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 today.
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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plan-pipeline:validate: 2-layer validation
Independently validate the plan produced by /plan-pipeline:start. No code is written. Run /clear after this command before running /plan-pipeline: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-pipeline: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.
- today First seen · 192 lines · 39 tokens per session scan A f4d83f7e234c
plan-pipeline-validate is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (43 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 1,591 once invoked, about $0.0002 per session on Opus 5.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-10-29.
Other skills, from other repositories
expo-eas-submit
App Store Connect and Google Play Console upload flow with EAS Submit, metadata, build-artifact selection, review notes, and phased release. Triggers on eas submit, app store connect, google play, asc api key, service account, metadata, screenshot, phased release, review notes, testflight, internal testing, production…
consulting
Strategic consulting skills for organizations. Long-term planning, business strategy, change management, organizational design, competitive analysis, vision/mission frameworks. Triggers on: strategy, consulting, planning, organizational change, competitive analysis, business model, vision.
product
Product management, strategy, user experience, development planning, and product analytics skills. Roadmapping, OKRs, JTBD frameworks, feature prioritization. Triggers on: product management, roadmap, OKR, JTBD, feature prioritization, product strategy, user research, MVP, PMF.
sales
Sales strategy, customer relationships, pipeline management, sales techniques, CRM, and sales analytics. Outbound, inbound, account-based selling, deal qualification frameworks (BANT, MEDDIC). Triggers on: sales, pipeline, CRM, prospecting, qualification, MEDDIC, BANT, deal review, sales playbook, account-based…
customer-success
Customer onboarding, retention, and success skills. Reduce churn through structured first-value moments, lifecycle messaging, NPS analysis, account health scoring. Triggers on: onboarding, customer success, retention, churn, NPS, customer health, lifecycle, expansion revenue.
productivity
Personal productivity, time management, project management, team productivity, automation, and process improvement skills. GTD, time-blocking, focus systems, async workflows. Triggers on: productivity, time management, GTD, focus, deep work, async, project management, workflow, habits.