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 agentmods add skills/instructa/planr/planr-statusnpx skills add instructa/planr --skill planr-statusgit clone --depth 1 https://github.com/instructa/planrWrote 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/instructa/planr/planr-status)<a href="https://agentmods.dev/skills/instructa/planr/planr-status"><img src="https://agentmods.dev/badge/skills/instructa/planr/planr-status.svg" alt="Measured on agentmods" 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 | $0.00048 | $0.00416 |
| Opus 5 | $0.00024 | $0.00208 |
| Sonnet 5 | $0.00010 | $0.00083 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
planr-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 4d 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 Status
Use read-only Planr commands first:
planr project show --json
planr map show --json
planr map lane --critical
planr map pressure
For one item:
planr trace item <item-id>
planr log list --item <item-id>
For active work, include runtime and approval state from trace item, map status, or:
planr approval list --open
planr pick stale --older-than-seconds 900
Goal Contract Check
When a loop or /goal run asks whether its stop condition holds, use the one-call verdict:
planr plan audit <plan-id> --json
planr evidence readiness --scope plan --id <plan-id>
planr evidence explain --scope plan --id <plan-id>
Audit answers holds: true/false from settled outcomes, explicitly required independent material ReviewGates, approvals, and canonical Evidence coverage. Binding Evidence success does not require a final product ReviewGate. Readiness reports configuration/runtime blockers before execution; explain reports exact receipt applicability and gaps. Report contract holds or contract open plus the exact unmet clauses straight from these outputs. Use planr search "GOAL CONTRACT" only to read the contract text itself.
Verdicts
Use one:
complete: closed with evidence and no open required child/review/approval work.in progress: concrete work remains and the next step is available.blocked: progress needs an external decision or prerequisite.unclear / partially verified: evidence is incomplete or inconsistent.
Never treat checked Markdown boxes or optimistic summaries as proof. Map state and log evidence decide.
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.
- 4d ago First seen · 53 lines · 48 tokens per session scan A 259e9ca78b79
planr-status is a skill published in the GitHub repository instructa/planr (71 stars, last pushed 7d ago), licensed MIT. It adds 48 tokens to every session and 416 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-30.
Other skills, from other repositories
meeting-transcript
Process meeting recordings and notes into structured decisions, action items, and team dynamics with intelligent noise filtering.
retro
CP-7 retrospective: audit checkpoints, evidence quality, action items, and harvest candidates. Closes the V-model cycle and feeds the next run. Use via /retro after ship, escalate, or significant session.
pad
Talk to your project. Natural-language project management — create items, check status, plan work, brainstorm ideas, and more.
pm-init
Skill "pm-init" from wei63w/pm-manager, covering user input, outline, 1. scaffold, 2. lifecycle and type and 3. detect spec kit (required).
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a…
pm-arch
Skill "pm-arch" from wei63w/pm-manager, covering user input, outline, done when and shared workflow (all /pm- commands).