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.orchestrategit 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.orchestrate)<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/flow.orchestrate"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/flow.orchestrate/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.orchestrate"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/flow.orchestrate.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.00025 | $0.05429 |
| Opus 5.5 | $0.00010 | $0.02172 |
| Sonnet 5.5 | $0.00005 | $0.01086 |
| Haiku 4.5 | $0.00003 | $0.00543 |
Grade A, and why
flow.orchestrate 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 — 672 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL RULES
YOU MUST FOLLOW THESE RULES WITHOUT EXCEPTION:
- NEVER edit
.specflow/orchestration-state.jsondirectly - Usespecflow state set - NEVER edit
tasks.mdto mark tasks complete - Usespecflow mark T### - NEVER skip steps - Execute in order: design → analyze → implement → verify
- ALWAYS verify step completion before advancing to next step
- ALWAYS use the SpecFlow CLI for all state and task operations
- NEVER STOP between steps - This is a CONTINUOUS workflow. After completing each step, immediately continue to the next step. Only stop at USER GATEs or when all steps are complete.
- Use
specflowdirectly, NOTnpx specflow- The CLI is installed at~/.claude/specflow-system/bin/specflow, not an npm package.
If you find yourself about to use the Edit tool on state files or tasks.md, STOP and use the CLI instead.
CONTINUOUS EXECUTION: Orchestration runs design → analyze → implement → verify in ONE session. Do not stop to ask "should I continue?" or report intermediate completion. Keep going until you reach a USER GATE or finish verify.
User Input
$ARGUMENTS
| Argument | Action |
|---|---|
(empty) or continue |
Resume from current state |
reset |
Clear state and restart current phase |
status |
Show status only, don't execute |
skip-to [step] |
Skip to step (design, analyze, implement, verify) |
Goal
Execute the complete SpecFlow development workflow with:
- State persistence - Survives conversation compaction
- Self-healing - Detects and recovers from inconsistencies
- Minimal user interaction - Only asks when truly necessary
- Auto-fix loop - Fixes ALL issues found during analyze until clean
Workflow Overview
| Step | Index | Command | Purpose | User Interaction |
|---|---|---|---|---|
| design | 0 | /flow.design |
Create all design artifacts | Progressive questions |
| analyze | 1 | /flow.analyze |
Cross-artifact consistency | Auto-fix loop |
| implement | 2 | /flow.implement |
Execute all tasks | Progress updates |
| verify | 3 | /flow.verify |
Verify completion | USER GATE if applicable |
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 · 672 lines · 25 tokens per session scan A 15995265e180
flow.orchestrate is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 5,429 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.