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.doctornpx skills add billbuchanan-code/claude-code-power-setup --skill flow.doctorgit 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.doctor)<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/flow.doctor"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/flow.doctor.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.00035 | $0.02159 |
| Opus 5 | $0.00017 | $0.01079 |
| Sonnet 5 | $0.00007 | $0.00432 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
flow.doctor 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 — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Arguments:
- Empty: Run diagnostics only (detect version, health check)
migrate: Run full migration with intelligent analysis--dry-run: Preview migration without changes
You MUST consider the user input before proceeding (if not empty).
Goal
Diagnose SpecFlow project state and optionally guide through migration:
- Detect current version (v1.0, v2.0, v3.0, or uninitialized)
- Analyze project health and compliance
- If migrating: run CLI upgrade + intelligent analysis
- Generate actionable migration guide with findings
Step 1: Detect Project Version
Run version detection:
specflow upgrade --dry-run --json
Parse the JSON to understand:
detection.version: Current version (v1.0, v2.0, v3.0, uninitialized)detection.confidence: How certain we are (high, medium, low)detection.indicators: What signals were found
Handle Special Cases
If uninitialized:
No SDD artifacts found in this repository.
This project has not been initialized with SpecFlow.
Would you like to:
1. Initialize as a new SpecFlow project → Run /flow.init
2. Exit and initialize manually
Use AskUserQuestion to get user choice.
If already v3.0:
This project is already at SpecFlow v3.0.
Run `specflow check` to validate project health.
Stop unless migrate was specified (to re-run analysis).
Step 2: Show Version Analysis
Display current state:
# Project Diagnosis
## Version Detection
| Property | Value |
| --------------- | ------------ |
| Current Version | {version} |
| Confidence | {confidence} |
| Target Version | v3.0 |
## Indicators Found
{list indicators}
## Required Migration Steps
{list steps from getMigrationSteps()}
If just running diagnostics (no migrate argument), show this and ask:
- "Run full migration?" → Proceed to Step 3
- "Exit" → Stop
Step 3: Run CLI Upgrade
If migrating, run the CLI upgrade command:
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 · 432 lines · 35 tokens per session scan A 4e466cda6c21
flow.doctor is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 2,159 once invoked, about $0.0002 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…