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.mergenpx skills add billbuchanan-code/claude-code-power-setup --skill flow.mergegit 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.00014 | $0.03925 |
| Opus 5 | $0.00007 | $0.01962 |
| Sonnet 5 | $0.00003 | $0.00785 |
| Haiku 4.5 | $0.00001 | $0.00392 |
Grade C, and why
flow.merge scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .specify/archive/${PHASE_NUMBER}-*/ How it starts
The opening of the file, as written. The whole thing — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Arguments:
- Empty: Close phase, push, create PR, merge, cleanup (default)
--pr-only: Create PR but don't merge (for review workflow)
Note: Use specflow directly, NOT npx specflow. It's a local CLI at ~/.claude/specflow-system/bin/.
Prerequisites
| Requirement | Check Command | If Missing |
|---|---|---|
| Verification passed | specflow status --json → step.status == complete |
Run /flow.verify |
| On feature branch | git branch --show-current (not main) |
Switch to phase branch |
| GitHub CLI installed | gh --version |
Install with brew install gh |
| Git remote configured | git remote -v |
Set up git remote |
| No merge conflicts | git merge-base main HEAD |
Rebase on main first |
Goal
Complete the current phase:
- Close the phase (update ROADMAP, archive, reset state)
- Commit the phase closure changes
- Push and merge to main
- Switch to main with clean state
Execution
0. Create Todo List
Create todo list immediately (use TodoWrite):
- [MERGE] PREFLIGHT - Verify branch and uncommitted changes
- [MERGE] VERIFY_GATE - Confirm verification passed
- [MERGE] CLOSE - Close phase via CLI
- [MERGE] COMMIT - Commit phase closure
- [MERGE] PUSH - Push and create PR
- [MERGE] MERGE - Merge PR to main
- [MERGE] MEMORY - Integrate archive into memory
- [MERGE] DONE - Report completion
Set [MERGE] PREFLIGHT to in_progress.
1. Pre-flight Checks
Verify on feature branch:
CURRENT_BRANCH=$(git branch --show-current)
if [[ "$CURRENT_BRANCH" == "main" || "$CURRENT_BRANCH" == "master" ]]; then
echo "ERROR: Cannot merge from main branch"
echo "Switch to a feature branch first"
exit 1
fi
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 · 524 lines · 14 tokens per session scan C 9e10020a541f
flow.merge is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 3,925 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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…