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.verifynpx skills add billbuchanan-code/claude-code-power-setup --skill flow.verifygit 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.00017 | $0.04330 |
| Opus 5 | $0.00009 | $0.02165 |
| Sonnet 5 | $0.00003 | $0.00866 |
| Haiku 4.5 | $0.00002 | $0.00433 |
Grade A, and why
flow.verify 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 — 570 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Arguments:
- Empty: Run full verification (tasks, checklists, memory, user gate)
--dry-run: Preview verification without updating state--skip-memory: Skip memory document compliance check
You MUST consider the user input before proceeding (if not empty).
Note: Use specflow directly, NOT npx specflow. It's a local CLI at ~/.claude/specflow-system/bin/.
Prerequisites
| Requirement | Check Command | If Missing |
|---|---|---|
| Implement gate passed | specflow check --gate implement |
Run /flow.implement |
| All tasks complete | specflow status --json → progress.percentage == 100 |
Complete remaining tasks |
| Checklists exist | specs/NNNN-name/checklists/ |
Run /flow.design --checklist |
| Constitution | .specify/memory/constitution.md |
Run /flow.init |
| Git branch | git branch --show-current |
Should be on phase branch |
Path clarification:
- Artifacts (spec.md, plan.md, tasks.md, checklists/):
specs/NNNN-name/fromcontext.featureDir - Phase definition (goals, scope):
.specify/phases/NNNN-*.md
Goal
Verify a completed feature phase is ready for merge:
- All tasks complete (or explicitly deferred)
- All checklists pass
- Implementation complies with memory documents
- User gate satisfied (if applicable)
Note: This command verifies readiness but does NOT close the phase. Use /flow.merge to close, push, and merge.
Step 0: Create Todo List
Create todo list immediately (use TodoWrite):
- [VERIFY] CONTEXT - Get project status and load phase artifacts
- [VERIFY] IMPL_GATE - Verify all tasks complete
- [VERIFY] VERIFY_GATE - Complete all checklists
- [VERIFY] PHASE_GOALS - Verify against original phase goals
- [VERIFY] MEMORY - Check against memory docs
- [VERIFY] REPORT - Mark verified and report
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 · 570 lines · 17 tokens per session scan A b6c229c55036
flow.verify is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 4,330 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.
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…
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.