A read-only delivery report for a project’s specifications, backlog items, and quick tasks. A pipeline is the tracked path from planning a feature to delivering it.

Use it to check one feature by its slug or produce a whole-project report, including references to GitHub pull requests and Linear work items.

It shows what is complete, what has failed, and what still needs work without changing project files.

status — Command for Claude Code by openplanr/planr-pipeline

Install

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.

Clone the repo

git clone --depth 1 https://github.com/openplanr/planr-pipeline

Made for: Claude Code.

Or install planr-pipeline, the plugin that ships this one along with the rest of its 8 skills, 10 commands, 1 hook.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/openplanr/planr-pipeline/status/github.svg)](https://agentmods.dev/commands/openplanr/planr-pipeline/status)

Your own site

<a href="https://agentmods.dev/commands/openplanr/planr-pipeline/status"><img src="https://agentmods.dev/badge/commands/openplanr/planr-pipeline/status/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/openplanr/planr-pipeline/status"><img src="https://agentmods.dev/badge/commands/openplanr/planr-pipeline/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,758 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00035	$0.01758
Opus 5.5	$0.00014	$0.00703
Sonnet 5.5	$0.00007	$0.00352
Haiku 4.5	$0.00003	$0.00176

Measured 1mo ago against content hash 5e6d614deca5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

status 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.

Origin

This is a copy

100% identical to status — 0 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.

commands/status.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/planr-pipeline:status [slug]

Read-only. Never mutates disk. Fatals use procedures/fatal-error-format.md.

Two modes:

No slug → whole-project delivery report (Step A): every Spec / Backlog item / Quick Task rolled up by status, cross-referenced with GitHub PRs + Linear from frontmatter, with a Summary and an Outstanding work section.
Slug → pipeline rollup for that spec/feature (Steps 0–3: marker, story/task counts, failures).

Step A — No slug: whole-project delivery report (v0.18.x parity)

The planr CLI is the deterministic engine for this report (planr status, src/services/delivery-status-service.ts); the plugin delegates to it so the two surfaces can never drift. Only when the CLI is absent do you compose the same report natively.

A.1 — Delegate when the CLI is installed AND new enough (preferred).

command -v planr && planr --version

The delivery report shipped in CLI 1.7.2 — an older planr would print the legacy tree instead. Delegate only when the version is ≥ 1.7.2 (compare with printf '%s\n1.7.2\n' "$(planr --version)" | sort -V | head -1 → must print 1.7.2). If so, run planr status --md (add --github / --linear only if the user explicitly asked for live cross-referencing) and print its output verbatim. Done — do not re-derive or "improve" the numbers; one engine, one truth.

A.2 — Fallback (no CLI, or CLI < 1.7.2): compose the same report from disk. Read-only, deterministic — never invent a status. When falling back because the CLI is outdated, append one line: Tip: npm i -g openplanr@latest enables the native engine (planr status --md).

Enumerate (mode per procedures/mode-detection.md):
- Specs: .planr/specs/SPEC-*/SPEC-*.md frontmatter → id, title, status (default mode: output/feats/feat-*/ with their .pipeline-shipped markers).
- Backlog: .planr/backlog/*.md → id, title, status, priority.
- Quick tasks: .planr/quick/*.md → id, title, status + checkbox counts (- [x] / - [ ]).
Classify every item: done (done|closed|completed|shipped|released) · addressed (promoted|superseded — resolved without being done; NOT outstanding, and never counted as done) · outstanding (everything else).
Cross-reference from frontmatter: linearIssueIdentifier (+ linearStatusReconciled as its state), githubIssue. If gh is authenticated you MAY best-effort correlate PRs by searching the artifact id in PR titles (gh pr list --search "<ID>" --state all --json number,title,mergedAt); label it best-effort, never as authoritative.
Render exactly this shape (the same as planr status --md):
- # <project> — Delivery Status + a source-of-truth note
- ## Summary — per category: **<Label>:** N done [+ M promoted/superseded] — T total, then **Outstanding:** none | N
- One ## <Category> table per non-empty category: | ID | Status | Title | Progress | PR | Linear |
- ## Outstanding work — list each open item (**ID** title — _status_), or None — every item is done or addressed (promoted/superseded).

Read the full file on GitHub · 137 lines

Changes

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 · 137 lines · 35 tokens per session scan A 5e6d614deca5

Subscribe to this mod's changes

status is a command published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 28d ago), licensed MIT. It adds 35 tokens to every session and 1,758 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to status, differing in 0 lines, and is treated as a copy.

Claude Code Code Generation Project management ai-agents claude-code-plugin spec-driven subagents

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.

btspoony/mstar-harness · 38 tokens

project-sprint

Sequential PDCA in the current session.

pactkit/claude-code-plugin · 7 tokens

octo-schedule

Manage scheduled workflow jobs for the Claude Octopus scheduler.

nyldn/claude-octopus · 24 tokens

octo-scheduler

Manage the Claude Octopus scheduled workflow runner daemon.

nyldn/claude-octopus · 15 tokens

Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…

grainulation/grainulator · 0 tokens

amazing-e2e-check

Run explicitly requested E2E, browser, device, or installed-deployment scenarios in an independent verification workflow.

btspoony/mstar-harness · 29 tokens