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-plannpx skills add instructa/planr --skill planr-plangit 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-plan)<a href="https://agentmods.dev/skills/instructa/planr/planr-plan"><img src="https://agentmods.dev/badge/skills/instructa/planr/planr-plan.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.00041 | $0.01102 |
| Opus 5 | $0.00020 | $0.00551 |
| Sonnet 5 | $0.00008 | $0.00220 |
| Haiku 4.5 | $0.00004 | $0.00110 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planr Plan
Read and apply the canonical Evidence ownership guard before product planning.
Use this when scope, ownership, acceptance criteria, or verification must be defined before implementation.
Workflow
planr project show --json
planr plan new "App idea" [--platform web] [--ai] [--backend]
planr plan refine <plan-id> --note "decision, constraint, or assumption"
planr plan check <plan-id>
planr plan split <plan-id> --slice "narrow implementation slice"
planr map build --from <build-plan-id>
Product Plan Standard
A product plan package must include:
- manifest;
- product spec;
- UX flows;
- design system;
- architecture;
- ADRs;
- AI spec when relevant;
- safety/privacy/security;
- API/data model;
- client and backend implementation specs;
- observability;
- QA;
- release readiness;
- executable tasks;
- references.
Build Plan Standard
A build plan must include:
- source plan;
- a non-empty
criteriafrontmatter list whose entries contain only a stableidandtitle; - scope decision;
- ownership target;
- existing leverage;
- phases;
- out of scope;
- verification;
- acceptance criteria.
Author criterion identity only in frontmatter, for example:
criteria:
- id: criterion-api-health
title: API health is observable from the target service
Keep the ## Acceptance Criteria section as readable narrative, never an identity source. Do not infer criterion IDs from prose or decide obligation completeness in this skill; plan check, explicit Evidence migration, and the canonical app/proof authority own those decisions.
For binding Evidence, inspect planr evidence policy --json and select existing named presets by
their observation semantics. The repository policy and registered capability—not the provider or
skill name in the user's prompt—own schemas and execution. If the policy default correctly covers
every criterion, no extra frontmatter is needed. Otherwise author only preset references beside the
closed criterion list:
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 · 113 lines · 41 tokens per session scan A 01b86e9d9df3
planr-plan is a skill published in the GitHub repository instructa/planr (71 stars, last pushed 7d ago), licensed MIT. It adds 41 tokens to every session and 1,102 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).