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.
git clone --depth 1 https://github.com/openplanr/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/plugins/openplanr/planr-pipeline/planr-pipeline)<a href="https://agentmods.dev/plugins/openplanr/planr-pipeline/planr-pipeline"><img src="https://agentmods.dev/badge/plugins/openplanr/planr-pipeline/planr-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/plugins/openplanr/planr-pipeline/planr-pipeline"><img src="https://agentmods.dev/badge/plugins/openplanr/planr-pipeline/planr-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
planr-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.
This is a copy
97% identical to planr-pipeline — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin.json",
"name": "planr-pipeline",
"version": "0.42.0",
"description": "Portable OpenPlanr PO, Design, Review, DEV, and QA pipeline with secure local artifact annotation and private sharing contracts.",
"author": {
"name": "OpenPlanr",
"url": "https://github.com/openplanr"
},
"homepage": "https://github.com/openplanr/planr-pipeline",
"repository": "https://github.com/openplanr/planr-pipeline",
"license": "MIT",
"keywords": [
"spec-driven",
"code-generation",
"subagents",
"pipeline",
"po-dev",
"openplanr",
"artifact-review"
]
}
What it installs
The manifest is a name and a version. 8 skills, 10 commands, 1 hook travel with it, and installing the plugin installs all of them — 490 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill planr-operate A 46 tokens
- Skill planr-artifact A 27 tokens
- Skill planr-ship A 20 tokens
- Skill planr-design A 21 tokens
- Skill planr-plan A 21 tokens
- Skill planr-dashboard A 17 tokens
- Skill planr-sync A 16 tokens
- Skill planr-doctor A 21 tokens
- Command ship A 28 tokens
- Command plan A 19 tokens
- Command operate A 18 tokens
- Command audit A 0 tokens
- Command design A 21 tokens
- Command status A 35 tokens
- Command dashboard A 46 tokens
- Command design-loop A 40 tokens
- Command design-review A 35 tokens
- Command sync A 59 tokens
- Hook Stop A not measured
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 · 23 lines scan A af24e3a1bf33
planr-pipeline is a plugin published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 28d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 97% identical to planr-pipeline, differing in 2 lines, and is treated as a copy.
Other plugins, from other repositories
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
commander-hub marketplace
Plugin marketplace listing 1 plugin: commander.
radin
Cost-optimized agentic workflow stack for solo devs: backlog orchestration (radin-batch, radin-plan, radin-review) plus curated companion tools.
transmuter
Transmute Framework — AI-driven pipeline that transforms a business plan into a fully deployed product through 25 stages (23 automated, 2 manual).
vp-beads
Sprint workflow automation: backlog grooming, retrospectives, upstream vendor tracking, cross-project synergy tracking, swarm wave orchestration, vendor sync, and bilateral sibling reconciliation for projects using beads and Basic Memory.
super-fr-dispatch
super-fr dispatch: queue phases to autonomous runners (VibeKanban adapter included) with per-PR quality gates.