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.analyzenpx skills add billbuchanan-code/claude-code-power-setup --skill flow.analyzegit 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.00015 | $0.02944 |
| Opus 5 | $0.00008 | $0.01472 |
| Sonnet 5 | $0.00003 | $0.00589 |
| Haiku 4.5 | $0.00002 | $0.00294 |
Grade A, and why
flow.analyze 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Note: Use specflow directly, NOT npx specflow. It's a local CLI at ~/.claude/specflow-system/bin/.
Prerequisites
| Requirement | Check Command | If Missing |
|---|---|---|
| Design gate passed | specflow check --gate design |
Run /flow.design |
| spec.md exists | specflow status --json → context.hasSpec |
Run /flow.design |
| plan.md exists | specflow status --json → context.hasPlan |
Run /flow.design |
| tasks.md exists | specflow status --json → context.hasTasks |
Run /flow.design |
| Constitution | .specify/memory/constitution.md |
Run /flow.init |
Goal
Analyze spec.md, plan.md, and tasks.md for inconsistencies, gaps, and quality issues. This command runs AFTER /flow.design has produced all artifacts. If it finds any issues, it will report on those issues in a detailed way, fix all issues (no matter how small), and then run /flow.analyze again.
Execution
0. Create Todo List
Create todo list immediately (use TodoWrite):
- [ANALYZE] INITIALIZE - Get project status and verify gate
- [ANALYZE] LOAD - Load all artifacts in parallel
- [ANALYZE] DETECT - Run 8 detection passes
- [ANALYZE] FIX - Auto-fix loop (max 5 iterations)
- [ANALYZE] REPORT - Generate analysis report
Set [ANALYZE] INITIALIZE to in_progress.
1. Initialize
specflow status --json
Parse response:
context.featureDir→ FEATURE_DIR (abort if null) - e.g.,/path/to/project/specs/0060-github-integrationphase.number→ PHASE_NUMBER (e.g., "0060")context.hasSpec/hasPlan/hasTasks→ all must be true
Path clarification:
FEATURE_DIR=specs/NNNN-name/- Active phase artifacts (spec.md, plan.md, tasks.md).specify/phases/NNNN-*.md= Phase definition document (goals, scope, verification 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 · 333 lines · 15 tokens per session scan A 05b8939c60a3
flow.analyze is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 2,944 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…