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-pipelinegit 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)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/plan-pipeline"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/plan-pipeline/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"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/plan-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 45 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00054 | $0.00688 |
| Opus 5.5 | $0.00022 | $0.00275 |
| Sonnet 5.5 | $0.00011 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
plan-pipeline 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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Pipeline Orchestrator
Orchestrates the complete plan-to-execution pipeline. Can run the full pipeline or a single isolated stage.
Stages
| Stage | Skill | Purpose |
|---|---|---|
| 1 | /plan-pipeline:ceo-review |
Challenge the brief, lock product direction |
| 2 | /plan-pipeline:eng-review |
Lock architecture, diagrams, and test matrix |
| 3 | /plan-pipeline:start |
5-phase planning: PRD, research, ADRs, task list |
| 4 | /plan-pipeline:validate |
2-layer validation before any code is written |
| 5 | /plan-pipeline:execute |
Worktree isolation, parallel agents, quality gate, PR |
Usage
/plan-pipeline # full pipeline, asks for context
/plan-pipeline --from=start # skip gates, start from planning phase
/plan-pipeline --from=validate # validate an existing plan
/plan-pipeline --from=execute # execute a validated plan
When to Use Each Stage
ceo-review: use before any significant feature when the direction is not locked. Especially valuable when the request is specific (specificity signals collapsed solution space).
eng-review: use after direction is locked. Required for features with async components, external dependencies, or multi-step flows.
start: use for any non-trivial feature touching more than 2 files or involving architecture decisions.
validate: always before execute. The cost of validation is negligible against the cost of discovering issues mid-execution.
execute: after validate confirms all issues are resolved.
Workflow
- Collect context: what are we building, and what stage do we start from?
- ceo-review: product direction gate (can be skipped with
--from=eng-reviewor later) - eng-review: architecture gate (can be skipped with
--from=startor later) - CHECKPOINT: ask user to confirm direction and architecture before planning
- start: run 5-phase planning, produce
docs/plans/plan-{name}.md - CHECKPOINT: present plan for review before validation
- validate: 2-layer validation (structural + specialist agents)
- execute: worktree isolation -> parallel agents -> quality gate -> 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.
- 1mo ago First seen · 71 lines · 54 tokens per session scan A b6e720c73fdb
plan-pipeline is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (42 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 688 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-09-04.
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.