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/skybao1024/sprint-flowWrote 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/commands/skybao1024/sprint-flow/sprint-done)<a href="https://agentmods.dev/commands/skybao1024/sprint-flow/sprint-done"><img src="https://agentmods.dev/badge/commands/skybao1024/sprint-flow/sprint-done.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.00014 | $0.00407 |
| Opus 5 | $0.00007 | $0.00204 |
| Sonnet 5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade B, and why
sprint-done scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/plugins/installed_plugins.json | grep -A 3 '"sprint-flow@sprint-flow-marketplace"' | grep installPath | cut -d'"' -f4 What it actually says
Sprint Done - Claude Code Wrapper
Independently verify and, when needed, repair a manually implemented Sprint Flow sprint using the shared done and loop specs.
Arguments: $ARGUMENTS (optional sprint number)
Resolve Plugin Root
Find PLUGIN_PATH:
cat ~/.claude/plugins/installed_plugins.json | grep -A 3 '"sprint-flow@sprint-flow-marketplace"' | grep installPath | cut -d'"' -f4
If empty, fall back to:
find ~/.claude/plugins -type d -name "sprint-flow" | grep -E "cache.*sprint-flow-marketplace" | head -1
Read {PLUGIN_PATH}/workflow/done-spec.md, {PLUGIN_PATH}/workflow/run-spec.md, and {PLUGIN_PATH}/workflow/loop-spec.md. Load verifier/repairer contracts, loop templates, the primary persona, relevant specialists, and the selected completion template before dispatch or finalization.
Claude Code Adaptation
- Use
$ARGUMENTSas the sprint number when supplied; otherwise use.sprint/config.jsoncurrent_sprint. - Use
CLAUDE.mdfrom config when generating next-session instructions. - Use
/sprint-run {N+1}as the next sprint command. - Use a fresh
Agent(...)verifier and sequential repair workers according to the shared loop spec. - Do not mark a sprint completed unless the latest complete independent verification cycle says
PASS. - If more sprints remain after
PASS, generate the next handoff and verification plan using the shared run and loop requirements. - Persist a blocked loop and surface its exact recovery action instead of treating manual completion intent as proof.
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 · 38 lines · 14 tokens per session scan B a10ad1c77822
sprint-done is a command published in the GitHub repository skybao1024/sprint-flow (5 stars, last pushed 21d ago), licensed MIT. It adds 14 tokens to every session and 407 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.