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-run)<a href="https://agentmods.dev/commands/skybao1024/sprint-flow/sprint-run"><img src="https://agentmods.dev/badge/commands/skybao1024/sprint-flow/sprint-run.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.01216 |
| Opus 5 | $0.00007 | $0.00608 |
| Sonnet 5 | $0.00003 | $0.00243 |
| Haiku 4.5 | $0.00001 | $0.00122 |
Grade B, and why
sprint-run 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 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.
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 How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Run - Claude Code Wrapper
You are the Claude Code orchestrator for Sprint Flow execution.
This command owns Claude Code tool use, plugin resource discovery, Agent dispatch, and AskUserQuestion clarification. The detailed execution and verification-loop quality bars live in the shared run and loop specs.
Arguments: $ARGUMENTS (optional sprint number, e.g. 3)
Step 1: Resolve Plugin Root
Find the installed Sprint Flow plugin root:
cat ~/.claude/plugins/installed_plugins.json | grep -A 3 '"sprint-flow@sprint-flow-marketplace"' | grep installPath | cut -d'"' -f4
Store the result as PLUGIN_PATH.
If empty, fall back to:
find ~/.claude/plugins -type d -name "sprint-flow" | grep -E "cache.*sprint-flow-marketplace" | head -1
Validate these files exist before continuing:
{PLUGIN_PATH}/workflow/run-spec.md{PLUGIN_PATH}/workflow/loop-spec.md{PLUGIN_PATH}/workflow/init-spec.md{PLUGIN_PATH}/personas/frontend-developer.md{PLUGIN_PATH}/personas/backend-developer.md{PLUGIN_PATH}/personas/fullstack-developer.md{PLUGIN_PATH}/personas/design-specialist.md{PLUGIN_PATH}/personas/api-integration-specialist.md{PLUGIN_PATH}/agents/sprint-executor.md{PLUGIN_PATH}/agents/sprint-verifier.md{PLUGIN_PATH}/agents/sprint-repairer.md{PLUGIN_PATH}/templates/implementation-report.md{PLUGIN_PATH}/templates/verification-plan.md{PLUGIN_PATH}/templates/verification-report.md{PLUGIN_PATH}/templates/repair-report.md{PLUGIN_PATH}/templates/completion-report-backend.md{PLUGIN_PATH}/templates/completion-report-frontend.md{PLUGIN_PATH}/templates/completion-report-fullstack.md
If the plugin root, shared specs, personas, agent contract, or templates cannot be found, stop and report the missing path.
Step 2: Load Shared Run Spec
Read {PLUGIN_PATH}/workflow/run-spec.md and {PLUGIN_PATH}/workflow/loop-spec.md completely.
Apply that shared spec for:
- sprint selection
- context preparation
- persona activation
- frontend/API context loading
- sprint clarification gate
- implementation worker prompt construction
- worker execution rules
- independent verification and repair cycles
- code quality and acceptance validation
- resumable loop state and circuit breakers
- completion validation
- next sprint handoff generation
- reporting and continuation
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 · 111 lines · 14 tokens per session scan B 309a71a8b154
sprint-run 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 1,216 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
implement
Execute tasks from a track's implementation plan following TDD workflow.
shipwright-enhance
Add features to an existing Shipwright project.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
aqa-flow
Router workflow for test automation: routes to ui-aqa-flow, api-aqa-flow, or testgen-flow. Kept for backward compatibility.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.