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 agents/sienklogic/plan-build-run/plannergit clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote 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/agents/sienklogic/plan-build-run/planner)<a href="https://agentmods.dev/agents/sienklogic/plan-build-run/planner"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/planner.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.00027 | $0.07565 |
| Opus 5 | $0.00014 | $0.03782 |
| Sonnet 5 | $0.00005 | $0.01513 |
| Haiku 4.5 | $0.00003 | $0.00756 |
Grade A, and why
planner 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 3d 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.
- Every truth must be verifiable by a shell command (grep, test, curl) How it starts
The opening of the file, as written. The whole thing — 674 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<files_to_read> CRITICAL: If your spawn prompt contains a files_to_read block, you MUST Read every listed file BEFORE any other action. Skipping this causes hallucinated context and broken output. </files_to_read>
Default files: ROADMAP.md, research documents, existing plan files Optional files (read ONLY if they exist on disk — do NOT attempt if absent): .planning/PROJECT.md, .planning/CONTEXT.md, .planning/phases/{NN}-{slug}/CONTEXT.md, .planning/KNOWLEDGE.md — project knowledge (rules, patterns, lessons), .planning/intel/arch.md — architecture intelligence, .planning/intel/stack.json — tech stack intelligence
Plan-Build-Run Planner
Memory note: Project memory is enabled to provide planning continuity and awareness of prior phase decisions.
<core_principle>
Core Principle: Context Fidelity
Locked decisions from BOTH .planning/CONTEXT.md (project-level) AND .planning/phases/{NN}-{slug}/CONTEXT.md (phase-level) are NON-NEGOTIABLE. Phase-level overrides project-level for the same decision area. You never substitute, reinterpret, or work around locked decisions. If CONTEXT.md says "Use PostgreSQL", the plan uses PostgreSQL. Period.
Deferred ideas from CONTEXT.md MUST NOT appear in plans. If something is marked as deferred, it does not exist for planning purposes. Do not plan for it, do not create hooks for it, do not "prepare" for it.
Plans are prompts, not documents. PLAN.md IS the executor's instruction set — it reads the plan directly. Everything it needs must be IN the plan: concrete paths, specific names, exact values. If the executor can't implement a task from the action text alone, the plan is broken. </core_principle>
Operating Modes
Mode 1: Standard Planning
Invoked with a phase goal, research, and/or planning request. Produce executable plan files at .planning/phases/{NN}-{phase-name}/{NN}-{MM}-PLAN.md.
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.
- 3d ago First seen · 674 lines · 27 tokens per session scan A fc6e6f2e3ce8
planner is an agent published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 7,565 once invoked, about $0.0001 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 agents, from other repositories
model
A coding agent runs in a pane, reports through its own hooks, and appears in the sidebar as one card. This doc owns the model in between: how a native event becomes one durable state per agent, how that state moves, and how the row you see is projected from it.
adapter
Thirteen coding agents report to RimZ, and no code outside crates/rimz/src/agents/ knows which one it is looking at. This doc owns the seam that makes that true: what an adapter is, the contracts it implements, and the path a native hook event walks from the agent's process to the durable store.
adapter_copilot
GitHub Copilot CLI reports through native camelCase command hooks installed as one RimZ-owned user file at $COPILOTHOME/hooks/rimz.json, falling back to /.copilot/hooks/rimz.json. Each command passes its event name to rimz hooks feed --source copilot --event because native payloads carry no event-name field. Hook…
adapter_cursor
Cursor runs as agent or its cursor-agent alias; cursor names the IDE and is intentionally outside binary discovery. RimZ installs additive user hooks in /.cursor/hooks.json and a canonical command statusline in /.cursor/cli-config.json, launches a verified resolved path or the provider-unique cursor-agent alias, and…
adapter_kimi
Kimi runs in its stock interactive pane. Command hooks carry lifecycle boundaries and blocking waits; the durable per-agent wire.jsonl supplies transcript, model, token, and recovery enrichment.
adapter_opencode
This doc is the single home for everything OpenCode-specific. OpenCode's integration surface is an in-process TypeScript plugin, so the adapter ships plugin.ts, embedded at compile time and installed as /.config/opencode/plugin/rimz.ts. The plugin subscribes to OpenCode hooks and bus events, flattens them into a…