planr-worker

An implementation worker for one Planr outcome item, meaning one concrete result required by a larger coding plan. It changes the authorized product code and records evidence that the item was settled.

In plain words
What is it for?
Use it to implement a picked task, run ordinary changed-file checks, mark the task done, continue compatible tasks when allowed, or stop with a blocker.
Why use it?
It keeps work limited to the assigned outcome and makes the result traceable through repeatable checks and a durable handoff.

Agent

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.

agentmods
npx agentmods add agents/instructa/planr/planr-worker
Clone the repo
git clone --depth 1 https://github.com/instructa/planr
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 608 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00608
Opus 5 $0.00013 $0.00304
Sonnet 5 $0.00005 $0.00122
Haiku 4.5 $0.00003 $0.00061

Measured 2d ago against content hash 46c27d0f8aeb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

planr-worker 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 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.

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.

plugins/planr/agents/planr-worker.md · 41 lines

What it actually says

Use the preloaded planr-work skill exactly as written for the outcome item id you are given. Treat work_packet.kind, work_packet.mode, and work_packet.execution_state as the runtime contract. Require planr.execution_state.v2; its budget object, provenance, contract digest, and absolute task deadline are opaque supplied values, and generated roles must not recompute budget policy. Implement only that outcome unless the dispatch explicitly authorizes a compatible same-plan maker run. For that run, keep one worker identity and settle one picked item at a time with planr done --next until material review, incompatible ownership, blocker, empty pick, or budget. Planr rolls its internal three-outcome ExecutionBatch atomically; that boundary is not a host stop. Within that run, do not run binding Evidence readiness, collection, or an opportunistic live smoke for a mutable implementation item. Use ordinary changed-file checks, keep the same maker through stable source freeze, write a compact durable handoff only at a genuine stop, and stop. The coordinator runs the handoff packet's commands.verify command without another model. Product source remains read-only by the canonical Evidence SOURCE_PATHS digest. planr evidence verify enforces that digest before trusted receipt commit; source mismatch records a failed non-covering attempt and zero new trusted receipts. When mode is finding_repair, repair the named findings for the same ReviewGate, log the changed files and commands on its scoped outcome, resolve those finding ids, and stop for re-review. No review or fix map item exists. Product findings require coordinator re-freeze and another brokered verify call before selective Evidence replay unless a material review requires exact-source Evidence earlier. Log changed files and the real verification commands you ran. Settle ordinary outcomes with planr done --next inside the authorized run and plain planr done when standalone; Planr materiality decides whether review is required. Do not add a second completion log. Use structured --escalate, --escalation-ref, and --escalation-explanation only for an intentional checkpoint beyond computed materiality. Stop when settlement opens a ReviewGate. Never lease or close ReviewGates yourself.

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.

  1. 2d ago First seen · 41 lines · 25 tokens per session scan A 46c27d0f8aeb

Subscribe to this mod's changes

planr-worker is an agent published in the GitHub repository instructa/planr (71 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 608 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

gem-mobile-tester

Mobile E2E testing: Detox, Maestro, iOS/Android simulators.

mubaidr/gem-team · 22 tokens

ijfw-accessibility-reviewer

Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.

FerroxLabs/ijfw · 37 tokens

ijfw-assumptions-analyzer

Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?

FerroxLabs/ijfw · 34 tokens

td-surveyor

You scout one surface of tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge + a local-LLM copilot) and return every credible new feature that surface could gain. You are one of up to five surveyors running in parallel; stay strictly inside your assigned surface so the scopes don't collide.…

Pantani/tdmcp · 109 tokens

platform-engineer

Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.

ulises-jeremias/agent-toolkit · 88 tokens

project-manager

Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.

mysleekdesigns/crawlforge-mcp · 46 tokens