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-worknpx skills add instructa/planr --skill planr-workgit clone --depth 1 https://github.com/instructa/planrWhat 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.00047 | $0.02071 |
| Opus 5 | $0.00023 | $0.01035 |
| Sonnet 5 | $0.00009 | $0.00414 |
| Haiku 4.5 | $0.00005 | $0.00207 |
Grade A, and why
planr-work scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Only the coordinator runs this command after source freeze. The configured method must be replayable: use a real shell command, host capture, or committed verifier, never prose such as "start server; curl /; check stats" How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planr Work
Read and apply the canonical Evidence ownership guard before product implementation. Do not duplicate or reinterpret it here.
Use this for one picked item at a time.
Workflow
Export your worker identity once per session so picks, logs, and heartbeats attribute to you instead of client:host:user:
export PLANR_WORKER_ID=maker-1
planr pick --json
The pick output is one flat typed packet. Branch only on work_packet.kind and, for outcome work, optional work_packet.mode; read lifecycle facts only from work_packet.execution_state. kind: "outcome" with an item id is ordinary maker work. kind: "outcome", mode: "finding_repair" has no synthetic fix item: repair the named findings on the same ReviewGate, log evidence against the gate's scoped outcome, resolve those finding ids, and stop for re-review. kind: "hold" is a stop, not permission to replace the maker or bypass policy. Each fact appears once; a missing key means "empty". No separate trace item call is needed. Add --work-type code to lease only outcome work while checker agents lease ReviewGates, and --plan <plan-id> when your dispatch names a plan. A null pick explains itself with a reason, remaining snapshot, exclusions, and a repair command when applicable. Read the linked plan/context, implement the smallest correct slice, then finish ordinary outcome work in one command:
Require work_packet.execution_state.schema_version to be planr.execution_state.v2. Treat its budget object—including consumed, reserved, protected, available, provenance, contract digest, and absolute task deadline—as opaque runtime authority. Skills must not recompute budget policy; a hold or unavailable required value is a stop.
planr done <item-id> --summary "what changed" --files path-a --files path-b --cmd "exact verification command" --tests "exact test command" --next
Use --next when the dispatch authorizes a compatible same-plan maker run. Settlement, the internal three-outcome batch rollover, and the next plan-scoped code lease then happen atomically. Omit --next for a standalone outcome.
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.
- 2d ago First seen · 91 lines · 47 tokens per session scan A 981064ace99b
planr-work is a skill published in the GitHub repository instructa/planr (71 stars, last pushed 6d ago), licensed MIT. It adds 47 tokens to every session and 2,071 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
etsy-category-listing
Etsy category page scraper: given an Etsy category URL (e.g. https://www.etsy.com/c/jewelry) and optional page number, returns paginated product listings with listingId, shopId, title, url, image, salePrice, originalPrice, currency, rating, reviewCount, shopName, isAd, freeShipping, badge from category and subcategory…
human-approval
Request human approval before performing a SAFETY-CRITICAL, IRREVERSIBLE, or SCOPE-EXPANDING action — submit a structured context (action, scope, risk, consequence) plus options, then STOP the current turn. The platform redispatches the agent after the human decides. NEVER use for routine deliverables (writing docs /…
firebase-analytics
Use when logging analytics events, setting user properties, configuring default event parameters, building funnels, or adding screen-view tracking.
firebase-remote-config
Use when implementing feature flags, running A/B tests, setting parameter defaults, fetching/activating config, or enabling real-time config updates.
git-master
MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git…
prismer-evolve-record
Record the outcome of applying an evolution strategy. Use after resolving an error where prismer-evolve-analyze provided a recommendation, to feed back success or failure to the network.