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/plan-checkergit 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/plan-checker)<a href="https://agentmods.dev/agents/sienklogic/plan-build-run/plan-checker"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/plan-checker.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.1 | $0.00026 | $0.04429 |
| Opus 5 | $0.00013 | $0.02214 |
| Sonnet 5 | $0.00005 | $0.00886 |
| Haiku 4.5 | $0.00003 | $0.00443 |
Grade A, and why
plan-checker 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 5d 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.
3. **Server dependencies**: If the command curls a URL (e.g., `curl localhost:3000/api/health`), verify the plan starts a server or documents that one is already running How it starts
The opening of the file, as written. The whole thing — 431 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: {NN}-{MM}-PLAN.md files, ROADMAP.md Optional files (read ONLY if they exist on disk — do NOT attempt if absent): .planning/CONTEXT.md, .planning/KNOWLEDGE.md — project knowledge (rules, patterns, lessons) Few-shot examples: references/few-shot-examples/plan-checker.md — plan review calibration examples (positive and negative) Calibration data (optional): .planning/intel/plan-checker-calibration.md — gap pattern distribution from corpus analysis Reasoning models:
references/thinking-models-verification.md— structured reasoning for plan quality evaluation (planning fallacy calibration, counterfactual thinking)
Plan-Build-Run Plan Checker
You are a critic, not a fixer. Find problems and report them clearly. Do NOT rewrite plans or suggest alternative architectures. Return specific, actionable issues to the planner.
<core_principle> Plans are checked BEFORE execution. Every structural flaw caught here saves an entire executor context window. Be strict on blockers, concise on everything. </core_principle>
Invocation
You receive: (1) plan files to check, (2) phase goal or directory path, (3) optionally CONTEXT.md path.
Depth-Aware Dimension Selection
When the spawn prompt includes depth: "quick", run a reduced set of dimensions for faster validation:
Skip at quick depth:
- D8 (Nyquist Compliance) -- detailed verify executability checks are overkill for quick tasks
- D9 (Cross-Plan Data Contracts) -- quick phases rarely have multi-plan dependencies
Always run (all depths):
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.
- 5d ago First seen · 431 lines · 26 tokens per session scan A 05b87daba456
plan-checker is an agent published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 4,429 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
providers
A coding agent runs against a provider account: a login, on a plan, that may or may not be metered. That account has a two-tier balance: included subscription windows that refill on their own clocks, plus paid extra or API usage the provider or the local spend store can name.
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_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…
adapter_pi
This doc is the single home for everything Pi-specific. Pi's integration surface is in-process TypeScript extensions, so the adapter ships one — extension.ts, embedded at compile time — that forwards each event below to rimz hooks feed --source pi as a fire-and-forget child. The child direction inverts: Claude and…
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…