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 skills add billbuchanan-code/claude-code-power-setup --skill flow.roadmapgit 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/flow.roadmap)<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/flow.roadmap"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/flow.roadmap/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/flow.roadmap"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/flow.roadmap.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.02305 |
| Opus 5.5 | $0.00010 | $0.00922 |
| Sonnet 5.5 | $0.00005 | $0.00461 |
| Haiku 4.5 | $0.00002 | $0.00231 |
Grade A, and why
flow.roadmap 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 1mo 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Arguments
| Argument | Description |
|---|---|
| (empty) | Generate or update ROADMAP.md |
add-pdr |
Convert PDRs to phases → Add PDR |
add-pdr --all |
Convert all approved PDRs |
backlog |
Triage backlog items → Backlog |
backlog --auto |
Auto-assign high-confidence matches |
| Other text | Use as project description for generation |
Execution
1. Initialize
specflow status --json
Parse response:
- Check if ROADMAP.md exists (via file system)
- Get project context if available
If ROADMAP.md exists, ask user:
- Update existing (add phases, update statuses)
- Replace entirely
- Cancel
2. Load Context
Read available sources (in priority order):
.specify/discovery/context.md- project type, criticality.specify/discovery/decisions.md- key architecture choices.specify/memory/constitution.md- core principles.specify/memory/tech-stack.md- technology stack- User input - vision, specific requirements
3. Apply Core Principles
CRITICAL: Prove Core Functionality First
The roadmap MUST follow this pattern:
- Core business logic FIRST (no UI, no database)
- POC test page to verify core logic works (USER GATE)
- Data layer (database, persistence)
- API layer exposing data
- API-integrated POC to verify data flow (USER GATE)
- External integrations (AI, payments, etc.) if applicable
- Integration POC to verify integrations (USER GATE)
- Production UI
- Complete UX POC (USER GATE)
- Admin capabilities if applicable
- Production hardening (PWA, performance, accessibility)
- Authentication (intentionally late - anonymous-first)
- Deployment (USER GATE)
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.
- 1mo ago First seen · 331 lines · 24 tokens per session scan A bb16cbf4e868
flow.roadmap is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 2,305 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.