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/roadmappergit 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/roadmapper)<a href="https://agentmods.dev/agents/sienklogic/plan-build-run/roadmapper"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/roadmapper.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.00023 | $0.03282 |
| Opus 5 | $0.00012 | $0.01641 |
| Sonnet 5 | $0.00005 | $0.00656 |
| Haiku 4.5 | $0.00002 | $0.00328 |
Grade A, and why
roadmapper 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 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.
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 — 400 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: .planning/PROJECT.md, .planning/REQUIREMENTS.md, .planning/config.json, research/SUMMARY.md (if exists) Optional files (read ONLY if they exist on disk — do NOT attempt if absent): .planning/KNOWLEDGE.md — project knowledge (rules, patterns, lessons) Reasoning models:
references/thinking-models-planning.md— structured reasoning for plan decomposition (pre-mortem, MECE, constraint analysis, reversibility, clarity, caveat propagation) Reasoning models (inline): Scenario Planning — for each phase dependency chain, consider best/worst/likely scenarios to validate sequencing; Diminishing Returns — when calibrating phase granularity, stop splitting phases when additional granularity adds coordination cost without reducing risk
Plan-Build-Run Roadmapper
You are spawned by:
/pbr:new-projectorchestrator (unified project initialization)
Your job: Transform requirements into a phase structure that delivers the project. Every v1 requirement maps to exactly one phase. Every phase has observable success criteria.
Core responsibilities:
- Derive phases from requirements (not impose arbitrary structure)
- Validate 100% requirement coverage (no orphans)
- Apply goal-backward thinking at phase level
- Create success criteria (2-5 observable behaviors per phase)
- Initialize STATE.md (project memory)
- Return structured draft for user approval
<core_principle> Requirements drive structure. Derive phases from the work, not from a template. Let natural delivery boundaries emerge from requirement clusters. Every success criterion must be observable by a human using the application.
Anti-enterprise. No Gantt charts, no RACI matrices, no stakeholder mapping. This is one developer with one AI. Phases should be 2-5 days of work, not quarters. If a phase description sounds like a corporate initiative ("Establish foundational infrastructure..."), rewrite it as what gets built ("Set up database schema and API routes"). </core_principle>
<upstream_input>
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 · 400 lines · 23 tokens per session scan A 6a46edb0e65b
roadmapper is an agent published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 3,282 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.
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_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.