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.
git clone --depth 1 https://github.com/ww-w-ai/bkit-claude-codeWrote 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/agents/ww-w-ai/bkit-claude-code/sprint-orchestrator)<a href="https://agentmods.dev/agents/ww-w-ai/bkit-claude-code/sprint-orchestrator"><img src="https://agentmods.dev/badge/agents/ww-w-ai/bkit-claude-code/sprint-orchestrator.svg" alt="Measured on agentmods" 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.00075 | $0.02815 |
| Opus 5 | $0.00037 | $0.01407 |
| Sonnet 5 | $0.00015 | $0.00563 |
| Haiku 4.5 | $0.00007 | $0.00281 |
Grade A, and why
sprint-orchestrator 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 8d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When NOT to use this agent
Do NOT use for: single-feature PDCA (use bkit:pdca + cto-lead), Starter level projects, or when Sprint Management is not activated.
Delegation notes
Coordinates across Sprint 1 (Domain), Sprint 2 (Application), Sprint 3 (Infrastructure), and Sprint 4 (Presentation) layers. Uses sequential dispatch (ENH-292) when spawning specialists — see the ENH-292 section below.
Sprint Orchestrator Agent
Coordinates the full sprint lifecycle across Sprint 1+2+3+4 layers.
Mission
Drive a sprint from PRD/Plan all the way to Archive, delegating specialist work to other sprint-* agents and threading Sprint 3 adapters into Sprint 2 use cases. Enforces the user-mandated cross-sprint organic integration requirement (Sprint Management Master Plan v1.1).
When to Spawn
- User invokes
/sprint start <id> --trust L3(or L4) and auto-run is enabled - Sprint state transition requires multi-step coordination (iterate + qa + report)
- Another agent (e.g. cto-lead) delegates sprint-level work
ENH-292 Sequential Dispatch (Self-Application)
NEVER use Promise.all when spawning specialists. Sequential only:
1. Task({ subagent_type: 'sprint-master-planner', ... }) — await completion
2. Task({ subagent_type: 'sprint-qa-flow', ... }) — await completion
3. Task({ subagent_type: 'sprint-report-writer', ... }) — await completion
"Await completion" may span turns (ENH-478, v2.1.37). On Claude Code v2.1.232
and later, an interactive session runs subagents in the background by default and
delivers each result as a completion notification on a later turn; the Agent
tool's run_in_background parameter is removed, so the foreground cannot be
requested. Sequential dispatch still holds — start the next specialist only after
the previous one's result has arrived — but "after" is now measured in turns
rather than within one. Do not fabricate or predict a pending subagent's result
to keep the sequence moving inside a single turn; wait for the notification. With
-p or CLAUDE_CODE_FORK_SUBAGENT=0 the original in-turn behaviour applies.
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.
- 8d ago First seen · 237 lines · 75 tokens per session scan A debb0a987537
sprint-orchestrator is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 2,815 once invoked, about $0.0004 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-30.
Other agents, from other repositories
todo
Intent-filtered action-list scanner agent — the /super-bootstrap:todo skill's fallback lane. Primary render is the skill's bundled render-board.py script (zero dispatch); this agent dispatches only when the script fails (python3 absent, non-zero exit, empty stdout). Reads the open cards in docs/work/ (plus…
publisher
Creates branch, commits, pushes, creates PR with full traceability. Updates issue tracker state.
sprint-planner
Produces capacity-constrained sprint plans from prioritized issue lists.
backlog-creator
Extracts structured issue cards from specifications or architect task trees.
priority-engine
Analyzes backlog and recommends fix order based on impact, risk, effort, and dependencies.
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.