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 commands/terryso/autoqa-agent/sprint-planninggit clone --depth 1 https://github.com/terryso/AutoQA-AgentWrote 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/terryso/autoqa-agent/sprint-planning)<a href="https://agentmods.dev/commands/terryso/autoqa-agent/sprint-planning"><img src="https://agentmods.dev/badge/commands/terryso/autoqa-agent/sprint-planning.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 | $0.00031 | $0.00198 |
| Opus 5 | $0.00015 | $0.00099 |
| Sonnet 5 | $0.00006 | $0.00040 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
sprint-planning 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 4d 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.
This is a copy
73% identical to correct-course — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
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.
- 4d ago First seen · 14 lines · 31 tokens per session scan A f05f94663862
sprint-planning is a command published in the GitHub repository terryso/AutoQA-Agent (134 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 198 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 73% identical to correct-course, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
index
Complete reference for all 20 BMAD Planning & Orchestrator skills. Invoked as /bmad-planning-orchestrator: or auto-triggered by Claude. Includes migration map from old slash commands.
modernize-preflight
Environment readiness check — analysis tools, build toolchain, source completeness, telemetry access.
modernize-status
Where am I in the modernization workflow — artifact inventory, staleness, secrets hygiene, next step.
delivery
Équipe de Livraison - Cycle de vie complet du sprint (rédaction + implémentation) utilisant les Agent Teams.
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.
auto-sprint
Orchestrateur de sprint de bout en bout (démarrage -> décomposition -> validation -> implémentation -> PR -> CI -> revue -> rétro -> merge).