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.initnpx skills add billbuchanan-code/claude-code-power-setup --skill flow.initgit 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.00004 | $0.02702 |
| Opus 5 | $0.00002 | $0.01351 |
| Sonnet 5 | $0.00001 | $0.00540 |
| Haiku 4.5 | $0.00000 | $0.00270 |
Grade A, and why
flow.init 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 yesterday.
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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecFlow Project Initialization
Initialize a project with SpecFlow by running a structured discovery interview, then generating governance documents.
Steps:
- Discovery Interview - Collect project context and decisions
- Constitution Generation - Create governance document from decisions
- Memory Documents - Generate tech-stack, coding-standards, etc.
- Roadmap Creation - Create initial ROADMAP.md
Each step is idempotent - if artifacts exist and appear complete, that step is skipped.
User Input
$ARGUMENTS
Arguments
| Argument | Action |
|---|---|
| (empty) | Run full initialization flow (or resume) |
status |
Show current progress |
--force |
Regenerate all artifacts even if complete |
faster |
Fast mode: 4 questions/round, skip optional phases |
deeper |
Deep mode: 2 questions/round, apply 5 Whys technique |
compare A vs B |
Compare two options side-by-side |
research TOPIC |
Research a topic before deciding |
| Other text | Use as project description, start interview |
Pre-Flight
Get project status:
specflow status --json
This tells us:
- Whether a phase is in progress (
phase.status) - What artifacts exist (
artifacts) - Project structure status
If orchestration is in progress (and not --force):
Active Phase Detected
Phase [number] is currently in progress.
Running /flow.init during active development is not recommended.
Options:
1. Complete the current phase with /flow.orchestrate
2. Run /flow.init --force to reinitialize anyway
If project structure doesn't exist (no .specflow/ or .specify/):
Recommend the CLI initialization first:
Project Not Initialized
Run `specflow init` first to create the project structure, then run `/flow.init` for discovery.
Or continue and /flow.init will create the structure for you.
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.
- yesterday First seen · 436 lines · 4 tokens per session scan A 49044de27866
flow.init is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 2,702 once invoked, about $0.0000 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…