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-plangit 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-plan)<a href="https://agentmods.dev/skills/openplanr/planr-pipeline/planr-plan"><img src="https://agentmods.dev/badge/skills/openplanr/planr-pipeline/planr-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/skills/openplanr/planr-pipeline/planr-plan"><img src="https://agentmods.dev/badge/skills/openplanr/planr-pipeline/planr-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.00021 | $0.00170 |
| Opus 5 | $0.00010 | $0.00085 |
| Sonnet 5 | $0.00004 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
planr-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 12d 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 PLAN
- Run
planr pipeline prepare-plan <feature> --jsonto resolve mode and scaffold a missing spec when appropriate. If it scaffolded a spec, stop so the user can edit it. - Read the returned spec,
input/tech/stack.md, optional database schema, and optional design spec. Follow the portable procedure incommands/plan.mdfrom the installed pipeline package. - Produce stories and tasks with no more than two tasks per story.
- Run
planr pipeline complete-plan <feature> --runtime codex --json. - Summarize the artifacts and stop. Never invoke SHIP automatically.
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.
- 12d ago First seen · 16 lines · 21 tokens per session scan A faf238f43a66
planr-plan is a skill published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 170 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
espalier-migrate
Migrate an existing harness/espalier install to the current Espalier version — auto-detects which of v0.1→v0.2, v0.3→v0.4, v0.4→v0.5, the v0.5.3 coder-agent patch, v0.5→v0.6 (Stage 1 grill), v0.6→v0.7 (read-only /espalier-ask lane), v0.7→v0.8 (requirements approval gate), the v0.8.1 impact-analysis agent patch, the…
mstar-conventions
A guide to Morning Star project folders, plan files, documentation boundaries, and Git branches. It explains where plans, specifications, iterations, knowledge, and project files belong.
mstar-routing-eval
A Chinese-language evaluation skill for checking whether software tasks are routed to the right agents and project checkpoints.
mstar-iteration
Use when starting, driving, resuming, or closing a Morning Star iteration, or running an autonomous Phase 1–5 loop — including without a slash command (e.g. 'start an iteration', 'drive the iteration', 'run an autonomous loop'). Manages Phase 1 (default interactive direction lock; opt-in autonomous), Autonomous…
mstar-compound-refresh
A knowledge-maintenance workflow for reviewing project knowledge documents, removing outdated material, merging overlaps, or creating a starter knowledge set from a codebase.
mstar-design-md
DESIGN.md design system specification for Morning Star projects. Create, audit, and maintain project-level design tokens (Colors, Typography, Spacing, Elevation, Motion, Shapes, Components, Voice & Content) using Vercel Geist as reference template. Three-level completeness checklist (MVP/Standard/Production) with…