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 skills/florianbruniaux/claude-code-plugins/plan-pipelinenpx 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.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.00054 | $0.00688 |
| Opus 5 | $0.00027 | $0.00344 |
| Sonnet 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 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 — 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.
- yesterday 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 (40 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 688 once invoked, about $0.0003 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 skills, from other repositories
analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…
doctor
OrchestKit doctor for health diagnostics across manifest integrity, hook configuration, skill validation, agent frontmatter, MCP server connectivity, CC version compatibility, and permission rules. Reports issues with severity levels and auto-remediation suggestions. Validates component counts, detects orphaned…
setup
创建一个新的 Workframe 项目，或把已有项目接入 Workframe。按用户意图与目标目录状态分流（新建 / 接入），对话采集业务上下文后落骨架、订阅 core 插件、完成落盘验收。仅用于 Workframe 框架的项目初始化，不承担 npm init / create-react-app / git init 等通用脚手架。.
code-review
代码审查，从需求符合度/正确性/安全性/可维护性/性能五维度评审代码变更，输出风险分级的 Finding 列表.
technical-design
技术方案设计与实施，提供轻量路径（小改动直接落地）和完整路径（架构/数据/API/多文件高风险变更走完整方案+实施+交付）双档分流.
competitive-analysis
结构化竞品分析，支持三类竞争对手识别、五维度深度分析、竞争矩阵与对战卡输出.