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/jjmartres/ai-coding-agentsWrote 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/jjmartres/ai-coding-agents/next-sprint-design)<a href="https://agentmods.dev/commands/jjmartres/ai-coding-agents/next-sprint-design"><img src="https://agentmods.dev/badge/commands/jjmartres/ai-coding-agents/next-sprint-design.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.00003 | $0.00214 |
| Opus 5 | $0.00002 | $0.00107 |
| Sonnet 5 | $0.00001 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
next-sprint-design 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 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.
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.
What it actually says
You are helping a DevOps engineer prepare a sprint kickoff message for Slack.
TEMPLATE STRUCTURE
Hey team, here is our next sprint design that will be publish on #squad-platform channel:
🚀 Sprint Kickoff - [Main Theme]
Hi team! Here's what we will be tackling this sprint:
[GROUPED STORIES WITH EMOJIS AND CONTEXT]
Questions? 👇
INSTRUCTIONS:
- Get Jira sprint stories: !
jira sprint list --next --table --plain - Analyze the JIRA stories and identify 2-4 main themes/epics
- Create sections with appropriate emojis
- Group related stories together logically (Using Epics)
- Explain business impact in plain language, not technical jargon
- Use the exact template structure above
- Keep it concise - aim for 3-5 bullet points per section max
- Replace [Main Theme] with the most prominent theme (e.g., "Cost Optimization & Hermes UX")
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 · 29 lines · 3 tokens per session scan A 17a6977924d8
next-sprint-design is a command published in the GitHub repository jjmartres/ai-coding-agents (45 stars, last pushed 2mo ago), licensed MIT. It adds 3 tokens to every session and 214 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
project-status
Show current project implementation status.
create-issue
Create GitHub issue with validated labels.
close-issue
../../knowledge/procedures/close-issue-procedure.md.
ponytail-debt
Harvest ponytail: comments into a tracked debt ledger.
runs
List live and persisted CCAM-launched Claude Code and Codex runs.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.