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/ww-w-ai/bkit-claude-code/sprintnpx skills add ww-w-ai/bkit-claude-code --skill sprintgit 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/skills/ww-w-ai/bkit-claude-code/sprint)<a href="https://agentmods.dev/skills/ww-w-ai/bkit-claude-code/sprint"><img src="https://agentmods.dev/badge/skills/ww-w-ai/bkit-claude-code/sprint.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.00081 | $0.07504 |
| Opus 5 | $0.00041 | $0.03752 |
| Sonnet 5 | $0.00016 | $0.01501 |
| Haiku 4.5 | $0.00008 | $0.00750 |
Grade A, and why
sprint 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 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.
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 — 608 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Skill — Generic Sprint Management for bkit Users
Sprint = meta-container above bkit's PDCA 9-phase. A sprint groups one or more features under a shared scope, budget, and timeline. Each sprint runs its own 8-phase lifecycle: prd -> plan -> design -> do -> iterate -> qa -> report -> archived.
Quick Start
/sprint init my-launch --name "Q2 Launch" --trust L3
/sprint start my-launch
The skill handler routes through <bkit-root>/scripts/sprint-handler.js
(bkit convention — handlers live at the bkit repo root scripts/ directory,
NOT inside skills//scripts/). The handler composes
Sprint 3 adapters (state-store + telemetry + doc-scanner + matrix-sync)
into Sprint 2 use cases (start / advance / iterate / qa / report / archive).
Sprint 1 entities (createSprint / SprintEvents / typedefs) are produced
and consumed transparently along the way.
Resolving
scripts/sprint-handler.jsin this document: throughout this SKILL.md, references toscripts/sprint-handler.jsmean<bkit-root>/scripts/sprint-handler.js(the canonical location). LLM dispatchers MUST NOT composeskills/sprint/scripts/sprint-handler.js— that path does not exist (Issue #107, fixed v2.1.19 S2 F2-1).
Arguments
| Argument | Description | Example |
|---|---|---|
init <id> |
Create a sprint with default config | /sprint init my-launch |
start <id> |
Run auto-run loop bounded by Trust Level scope | /sprint start my-launch --trust L3 |
status <id> |
Show current sprint state from disk | /sprint status my-launch |
list |
Union of state-store entries and master-plan discoveries | /sprint list |
phase <id> --to <phase> |
Advance to a specific phase | /sprint phase my-launch --to qa |
iterate <id> |
Run matchRate-100 loop (max 5 cycles) | /sprint iterate my-launch |
qa <id> --feature <name> |
Run 7-Layer data-flow check on one feature | /sprint qa my-launch --feature auth |
report <id> |
Generate KPI + lessons + carry-items report | /sprint report my-launch |
archive <id> |
Move to terminal archived status |
/sprint archive my-launch |
pause <id> |
Manually pause a running sprint | /sprint pause my-launch |
resume <id> |
Re-evaluate triggers and resume | /sprint resume my-launch |
watch <id> |
Live dashboard (Sprint 5 — current returns snapshot) | /sprint watch my-launch |
feature <id> |
Per-feature operations (Sprint 5) | /sprint feature my-launch --feature auth |
fork <id> |
Fork into a new sprint (Sprint 5) | /sprint fork my-launch --new my-launch-v2 |
help |
Print sub-action help | /sprint help |
master-plan <project> |
Generate multi-sprint Master Plan (agent isolated spawn) | /sprint master-plan q2-launch --name "Q2 Launch" --features auth,payment |
measure <id> |
Measure single gate / multi-gate / phase batch (v2.1.16 #94) | /sprint measure my-launch --gate M4 |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 608 lines · 81 tokens per session scan A 7f0a1c52a4b6
sprint is a skill published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed today), licensed Apache-2.0. It adds 81 tokens to every session and 7,504 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-09-03.
Other skills, from other repositories
magazine-web-ppt
For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.
stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows.
html-ppt-zhangzara-broadside
OpenDesign's product-launch announcement and press narrative — the headline, the proof points, and the call to action. Built as a decision-grade marketing & GTM deck for press, community, prospects.
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.
deck-guizang-editorial
OpenDesign's FY26 marketing plan: brand-to-pipeline — audience, offer, channel mix, and the launch calendar that ties creative to growth. Built as a decision-grade marketing & GTM deck for CMO, growth lead, founder.
drug-design
End-to-end drug discovery pipeline orchestration. Deterministic Python script that auto-chains structure prediction, pocket detection, de novo design, docking, scoring, and ADMET filtering into reproducible workflows.