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/billbuchanan-code/claude-code-power-setup/roadmap-reviewnpx skills add billbuchanan-code/claude-code-power-setup --skill roadmap-reviewgit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWrote 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/skills/billbuchanan-code/claude-code-power-setup/roadmap-review)<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/roadmap-review"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/roadmap-review.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.00097 | $0.03236 |
| Opus 5 | $0.00048 | $0.01618 |
| Sonnet 5 | $0.00019 | $0.00647 |
| Haiku 4.5 | $0.00010 | $0.00324 |
Grade A, and why
roadmap-review 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executive Reviewer Panel — Orchestration Skill
You are the orchestrator for the 9-person Executive Reviewer Panel. Your job is to spawn reviewer agents in parallel, collect their scored assessments, synthesize a dashboard, and present an actionable recommendation triage for the user.
Arguments
$ARGUMENTS
Parse arguments for:
- Reviewer filter: If specific reviewer names are listed (e.g.,
ceo coo cfo), run only those reviewers. If no names given, run ALL 9. - Product filter: If
--product <name>is specified, focus reviews on that single product. Otherwise review all 7. - Round number: If
--round <N>is specified, label this as Review Round N. Otherwise detect from existing files indocs/reviews/.
Valid Reviewer Names
ceo, coo, cmo, cco, cfo, cto, talent, analyst, client
Phase 1: Gather the Roadmap Package
Before spawning reviewers, assemble the full context they need. Read these files and build a ROADMAP_PACKAGE variable:
Required Files (read all in parallel)
docs/roadmap/master-roadmap.md
docs/roadmap/year-1-priorities.md
docs/synthesis/cross-cutting-themes.md
docs/roadmap-docs/00-tracker.md
decisions/decision-log.md
evidence/evidence-center.md
docs/capacity/owner-load.md
Product Roadmap Files (read all 7)
docs/roadmap-docs/01-media.md
docs/roadmap-docs/02-search.md
docs/roadmap-docs/03-creative-and-brand.md
docs/roadmap-docs/04-web-development.md
docs/roadmap-docs/05-data-and-decision-sciences.md
docs/roadmap-docs/06-crm-and-lifecycle.md
docs/roadmap-docs/07-strategy-and-consulting.md
Supporting Files (read in parallel)
docs/internal-briefs/01-media.md (through 07)
docs/market-briefs/01-media.md (through 07)
docs/framework-review/08-talent-model.md
docs/framework-review/09-tooling-and-data.md
docs/framework-review/year-3-end-states.md
docs/framework-review/reviewer-panel.md
If --product <name> was specified, only read the relevant product's roadmap, internal brief, and market brief.
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 · 362 lines · 97 tokens per session scan A 3009beb8166c
roadmap-review is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 3,236 once invoked, about $0.0005 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…