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/rules/openplanr/planr-pipeline/planr-pipeline-ship)<a href="https://agentmods.dev/rules/openplanr/planr-pipeline/planr-pipeline-ship"><img src="https://agentmods.dev/badge/rules/openplanr/planr-pipeline/planr-pipeline-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/rules/openplanr/planr-pipeline/planr-pipeline-ship"><img src="https://agentmods.dev/badge/rules/openplanr/planr-pipeline/planr-pipeline-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.00032 | $0.02717 |
| Opus 5 | $0.00016 | $0.01358 |
| Sonnet 5 | $0.00006 | $0.00543 |
| Haiku 4.5 | $0.00003 | $0.00272 |
Grade A, and why
planr-pipeline-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 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.
How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship {feature} — DEV Phase orchestration (Cursor)
When the user says "ship {feature}" (or "implement {feature}", "build
{feature}"), follow this rule end-to-end. The argument {feature} is the
feature slug.
Per R1, this command MUST NOT be auto-chained from "plan {feature}". The user must explicitly invoke it after reviewing the PO-phase output.
Mirrored argv flags (--task T-NNN, --yes, --no-devops, --no-docs): see upstream commands/ship.md + commands/procedures/ship-arguments-and-cost-gate.md.
Step 0 — Snapshot sentinel
Cursor has no Stop hook (unlike Claude Code). To approximate the same
"reminder if /ship aborts before snapshot" guarantee, write
.cursor/.snapshot-pending (empty file) at the start of this rule. If a
later run encounters this sentinel, surface a one-line reminder to refresh
CLAUDE.md (Step 5) before proceeding.
Step 0.5 — Parse argv (upstream Phase A only)
Strip flags first; leftover token is {feature} slug. Record $SHIP_SKIP_DEVOPS,
$SHIP_SKIP_DOCS, $SHIP_ASSUME_YES, $SHIP_TASK_ID.
Do NOT mutate disk here.
Step 1 — Mode detection + input validation (+ Phase B COST gate)
1a — Detect planr spec mode
Same as planr-pipeline-plan.mdc Step 1a:
- If
.planr/config.jsonhasidPrefix.specset, spec-driven mode. SPEC_DIR = .planr/specs/<SPEC-NNN-{feature}>/.- Otherwise, default mode (
output/feats/feat-{feature}/).
| Concept | Default | Spec-driven |
|---|---|---|
| Feature root | output/feats/feat-{feature}/ |
<SPEC_DIR>/ |
| US files | output/feats/feat-{feature}/us-*/us-*.md |
<SPEC_DIR>/stories/US-*.md |
| Task files | output/feats/feat-{feature}/us-*/tasks/task-*.md |
<SPEC_DIR>/tasks/T-*.md |
Failure handoff (per task id) |
…/feat-{feature}/us-{N}/tasks/T-<TASK_ID>-error-report.md |
<SPEC_DIR>/tasks/T-<TASK_ID>-error-report.md |
| QA report | output/feats/feat-{feature}/qa-report.md |
<SPEC_DIR>/qa-report.md |
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 · 261 lines · 32 tokens per session scan A c69b8c26fc60
planr-pipeline-ship is a cursor rule published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 2,717 once invoked, about $0.0002 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 cursor rules, from other repositories
mstar-cursor-plan-mode
When using Cursor Plan mode with Morning Star, dual-write CreatePlan to .mstar/ harness artifacts and require per-task commits.
mstar-entry
Ensure Morning Star core skill is loaded first in Cursor plugin usage.
archcore-context
Archcore knowledge base context — document types, MCP tools, and conventions for working with .archcore/ documents.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
neuraforge
NeuraForge AI — Architecture Principles.
debug
Read agents/debug.md for full instructions. Follow AGENTS.md for architecture principles.