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/flow.roadmapnpx skills add billbuchanan-code/claude-code-power-setup --skill flow.roadmapgit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWhat 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.00024 | $0.02305 |
| Opus 5 | $0.00012 | $0.01153 |
| Sonnet 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 2d 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.
- 2d 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 1mo ago), licensed MIT. It adds 24 tokens to every session and 2,305 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-31.
Other skills, from other repositories
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.