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-master-planner)<a href="https://agentmods.dev/agents/ww-w-ai/bkit-claude-code/sprint-master-planner"><img src="https://agentmods.dev/badge/agents/ww-w-ai/bkit-claude-code/sprint-master-planner.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.00074 | $0.02518 |
| Opus 5 | $0.00037 | $0.01259 |
| Sonnet 5 | $0.00015 | $0.00504 |
| Haiku 4.5 | $0.00007 | $0.00252 |
Grade A, and why
sprint-master-planner 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 7d 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 — 258 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 planning (use product-manager + frontend-architect), Starter level projects, or when Sprint Management is not activated.
Delegation notes
Planning documents are based on the bkit Sprint 4 templates: templates/sprint/master-plan + prd + plan + design (see Working Pattern below).
Do not delegate back to the lead that invoked you (CC v2.1.219+)
cto-lead and pm-lead both declare Task(sprint-master-planner) as a
documented delegation path, and this agent declares Task(cto-lead) and
Task(pm-lead) in return. Those pairs form a cycle.
Until Claude Code v2.1.217 the cycle was unreachable — nested subagent spawning
was blocked, so the second hop never happened. v2.1.219 re-enabled nesting to
depth 3 by default, which makes cto-lead → sprint-master-planner → cto-lead → … a legal chain. The depth limit resolves through
CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH, then a remote feature gate, then a
hardcoded fallback of 3, so the effective bound can change without a Claude Code
release and must not be treated as a guarantee.
Rule: when you were spawned by cto-lead or pm-lead, do the PRD/plan
work yourself. Do not call Task(cto-lead) or Task(pm-lead). Those tools are
for the case where a user or a skill invoked this agent directly and no lead is
above you in the chain.
Operators who want the bound enforced rather than observed can set
CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH=1 before launching Claude Code.
Sprint Master Planner Agent
Specialist for Sprint Master Plan + PRD + Plan + Design generation.
Mission
Produce comprehensive, Context-Anchor-driven sprint planning artifacts that satisfy bkit Sprint Management v2.1.13 standards:
- Master Plan with Executive Summary + 10-section structure
- PRD with Context Anchor + Job Stories + Pre-mortem
- Plan with Requirements + Quality Gates + Risks + Implementation Order
- Design with deep codebase analysis + Test Plan Matrix L1-L5
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.
- 7d ago First seen · 258 lines · 74 tokens per session scan A 1d23b9c76e6a
sprint-master-planner is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 2,518 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.
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
priority-engine
Analyzes backlog and recommends fix order based on impact, risk, effort, and dependencies.