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-status)<a href="https://agentmods.dev/commands/skybao1024/sprint-flow/sprint-status"><img src="https://agentmods.dev/badge/commands/skybao1024/sprint-flow/sprint-status.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.00008 | $0.00338 |
| Opus 5 | $0.00004 | $0.00169 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade B, and why
sprint-status 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 Status - Claude Code Wrapper
Show Sprint Flow status in Claude Code using the shared status spec.
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/status-spec.md and {PLUGIN_PATH}/workflow/loop-spec.md. If unavailable, still show basic status from .sprint/config.json, .sprint/iteration-plan.md, and any loop-state file, but report which shared spec was missing.
Claude Code Adaptation
- Use
/sprint-init <prd>as the init command in next-action text. - Use
/sprint-run [N]as the run command in next-action text. - Use
/sprint-done [N]only for manual completion. - If
$ARGUMENTScontains a sprint number, show detailed status for that sprint. - Show the loop phase, cycle, latest result/report, gate counts, failed gate IDs, active verifier/repairer, blocker, and recovery action when loop state exists.
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 · 36 lines · 8 tokens per session scan B 0fee5fbf8c86
sprint-status is a command published in the GitHub repository skybao1024/sprint-flow (5 stars, last pushed 21d ago), licensed MIT. It adds 8 tokens to every session and 338 once invoked, about $0.0000 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.