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 skills add billbuchanan-code/claude-code-power-setup --skill flow.analyzegit 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.analyze)<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/flow.analyze"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/flow.analyze/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/flow.analyze"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/flow.analyze.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00015 | $0.02944 |
| Opus 5.5 | $0.00006 | $0.01178 |
| Sonnet 5.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 1mo 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.
- 1mo 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 2mo ago), licensed MIT. It adds 15 tokens to every session and 2,944 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.