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.designnpx skills add billbuchanan-code/claude-code-power-setup --skill flow.designgit 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.00025 | $0.05735 |
| Opus 5 | $0.00013 | $0.02867 |
| Sonnet 5 | $0.00005 | $0.01147 |
| Haiku 4.5 | $0.00003 | $0.00573 |
Grade A, and why
flow.design 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 — 714 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Arguments
| Flag | Effect |
|---|---|
| (none) | Full flow: discover → spec → plan → tasks → checklists |
--spec |
Cascade from spec: spec → plan → tasks → checklists |
--plan |
Cascade from plan: plan → tasks → checklists |
--tasks |
Cascade from tasks: tasks → checklists |
--checklist |
Regenerate only checklists |
Note: Use specflow directly, NOT npx specflow. It's a local CLI at ~/.claude/specflow-system/bin/.
Prerequisites
| Requirement | Check Command | If Missing |
|---|---|---|
| Active phase | specflow phase |
Run specflow phase open <number> |
| Phase document | .specify/phases/NNNN-*.md |
Create phase in ROADMAP.md first |
| Constitution | .specify/memory/constitution.md |
Run /flow.init |
| Git branch | git branch --show-current |
Should be on phase branch |
Goal
Produce all design artifacts for the current phase.
Artifact Location: specs/{PHASE_NUMBER}-{phase-name}/ at project root.
- Example: Phase 0060 "GitHub Integration" →
specs/0060-github-integration/ - NOT
.specify/phases/- that's for phase definition files only
| Artifact | Location |
|---|---|
discovery.md |
specs/NNNN-name/discovery.md |
spec.md |
specs/NNNN-name/spec.md |
requirements.md |
specs/NNNN-name/requirements.md |
ui-design.md |
specs/NNNN-name/ui-design.md (if UI phase) |
plan.md |
specs/NNNN-name/plan.md |
tasks.md |
specs/NNNN-name/tasks.md |
checklists/implementation.md |
specs/NNNN-name/checklists/implementation.md |
checklists/verification.md |
specs/NNNN-name/checklists/verification.md |
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 · 714 lines · 25 tokens per session scan A 27ab9cc46a3e
flow.design is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 5,735 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
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…