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 openplanr/planr-pipeline --skill planr-shipgit 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/skills/openplanr/planr-pipeline/planr-ship)<a href="https://agentmods.dev/skills/openplanr/planr-pipeline/planr-ship"><img src="https://agentmods.dev/badge/skills/openplanr/planr-pipeline/planr-ship/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/openplanr/planr-pipeline/planr-ship"><img src="https://agentmods.dev/badge/skills/openplanr/planr-pipeline/planr-ship.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.00020 | $0.00225 |
| Opus 5 | $0.00010 | $0.00112 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
planr-ship 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 11d 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.
What it actually says
Planr SHIP
- Confirm this is a separate user invocation after PLAN review.
- Run
planr pipeline prepare-ship <feature> --json, then follow the portable procedure incommands/ship.mdfrom the installed pipeline package — the same one procedure the Claude Code command reads, so this workflow has one implementation. Execute ready tasks independsOnorder (native subagents when available, otherwise the registry-defined roles sequentially), respect each task's Create/Modify/Preserve lists and role ownership, and retry a failing task at most three times before writing its error report and marking it blocked. - Run build and tests from
input/tech/stack.md, perform the read-only QA gate, then runplanr pipeline finalize-ship <feature> --runtime codex --jsonso manifests, provenance, and the.pipeline-shippedmarker are written.
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.
- 11d ago First seen · 18 lines · 20 tokens per session scan A 17da8459a465
planr-ship is a skill published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 225 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
mstar-project-governance
A project-management rulebook for writing project roadmaps and tracking unresolved issues. A roadmap describes project direction, while a residual register records open problems until they are verified as closed.
pm
PM entry shim — force project-manager orchestration when user invokes /pm or this skill (Codex, Cursor, OpenCode, Kimi, ZCode, and omp). General per-plan PM work: this skill + project-manager.md. Formal iteration lifecycle: mstar-iteration (host commands/ may orchestrate Phase 1–5). Boot, routing, dispatch SSOT →…
feedback
Processes user feedback batches through the spec-update-code-test-docs chain. This skill should be used when the user asks to "process user feedback", "run the feedback loop", "analyze user feedback", "implement feedback changes", "triage support tickets", "run stage 8", "process feedback batch", or "update specs from…
domain-setup
Configure your industry domain, country, and regulatory context — agents automatically adapt to your business.
scaffold
Bootstrap a new project with your stack, auth, database, and standards pre-configured.
pactkit-board
Sprint Board atomic operations: add Story, update Task, archive completed Stories.