Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add openplanr/planr-pipeline/plugin install planr-pipelineWrote 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/openplanr/planr-pipeline/plan)<a href="https://agentmods.dev/commands/openplanr/planr-pipeline/plan"><img src="https://agentmods.dev/badge/commands/openplanr/planr-pipeline/plan/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/commands/openplanr/planr-pipeline/plan"><img src="https://agentmods.dev/badge/commands/openplanr/planr-pipeline/plan.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.00019 | $0.02154 |
| Opus 5.5 | $0.00008 | $0.00862 |
| Sonnet 5.5 | $0.00004 | $0.00431 |
| Haiku 4.5 | $0.00002 | $0.00215 |
Grade A, and why
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 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/planr-pipeline:plan {feature-name}
Orchestrates the PO Phase for feat-{slug} (first token after flag stripping — see plan-step0-preflight.md). Decomposes a functional spec into User Stories + Tasks, optionally with a design spec from PNG mockups and a DB schema snapshot.
Flags: --dry-run — executes read-only plan-dry-run-preview.md immediately after plan-step0-preflight.md § 0.5 and STOPs (no Phase B→D; no PO subagents; no orchestration writes in that invocation beyond anything already flushed before § 0.5b). Fatal errors obey fatal-error-format.md (two-line).
The PO Phase NEVER auto-chains to the DEV Phase. This command stops after writing US/task files. A human must review the generated stories + tasks before invoking /planr-pipeline:ship $ARGUMENTS. This is enforced by ${CLAUDE_PLUGIN_ROOT}/docs/rules.md R1.
ORCHESTRATION CONTRACT (read this first, mandatory)
This command has EXACTLY these phases, in order:
| Phase | Purpose | Outputs |
|---|---|---|
| A — Pre-flight | Parse args, set up project state | .planr/config.json, input/tech/stack.md (when applicable) |
| B — Mode + spec body | Detect mode, author spec body from BRIEF | <SPEC_DIR>/SPEC-NNN-${SLUG}.md with substantive content |
| C — Subagent dispatch | Run db-agent → designer-agent → specification-agent | DB snapshot, design-spec.md, US/Task files |
| D — R1 gate (stop) | Verify completion + print summary + stop | Console summary, NO /ship chain |
Termination rule
You are NOT done when a Bash command succeeds. You are NOT done when scaffolding completes. You are NOT done when bootstrap files are written.
You are done ONLY when the Completion Contract in ${CLAUDE_PLUGIN_ROOT}/procedures/plan-steps-2-through-completion.md is satisfied — every checkbox verified on disk.
If you cannot complete a phase (subagent fails, scaffolder fails, missing dep), abort with a clear error identifying which phase failed and what state was reached. Do not print success. Do not silently exit.
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 · 122 lines · 19 tokens per session scan A 6058d8a5ce15
plan is a command published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 28d ago), licensed MIT. It adds 19 tokens to every session and 2,154 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
iteration-loop
Run a whole iteration Phase 1→6 autonomously — code-first direction lock with a retained prototype, then execute → close → PR → merge-ready → post-merge close. Optional direction hint and scale S|M|L|XL; explicit autonomous opt-in, no grill-me, no routine confirmation.
iteration-drive
Drive or resume the selected locked iteration through Phase 2→6 — autonomous execute → iteration-close → PR → merge-ready loop → post-merge close. Takes no arguments.
codebase-audit
Read-only codebase survey — a prioritized, evidence-backed review report of what is worth doing. Use standalone or before /iteration-start; scope keywords pick the effort level and focus. Never edits source.
amazing-e2e-check
Run explicitly requested E2E, browser, device, or installed-deployment scenarios in an independent verification workflow.
init
First-time Archcore setup — wire host configs, measure the authored context, compose the full first-day seed in one preview, and create it on one confirm; import converts CLAUDE.md, AGENTS.md, rule files, ADRs, and docs into native documents; refresh adds new facts or drills into one domain.
document
Record the present state by mode — decision (ADR, RFC, rule), code (spec, doc, guide, scenario), or research (a ready report or one external material); a gate picks the document type.