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 skills/theshadow27/mcp-cli/sprintnpx skills add theshadow27/mcp-cli --skill sprintgit clone --depth 1 https://github.com/theshadow27/mcp-cliWrote 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/skills/theshadow27/mcp-cli/sprint)<a href="https://agentmods.dev/skills/theshadow27/mcp-cli/sprint"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/sprint.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.00069 | $0.01366 |
| Opus 5 | $0.00034 | $0.00683 |
| Sonnet 5 | $0.00014 | $0.00273 |
| Haiku 4.5 | $0.00007 | $0.00137 |
Grade A, and why
sprint 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint
The sprint lifecycle has four phases. Route based on arguments:
| Input | Action |
|---|---|
/sprint plan |
→ Read references/plan.md |
/sprint (sprint plan exists) or /sprint <N> (sprint number matching a plan file) |
→ Auto-chain: read references/run.md and execute run; at wind-down, read references/review.md and execute the release inline; then read references/retro.md and execute the retro inline — all in the same session, no re-invocation |
/sprint run or /sprint run <N> |
→ Run-only: read references/run.md and execute; mark the sprint-plan header with (RUN ONLY) next to the "Started …" timestamp; stop at wind-down without review/retro |
/sprint <issue-numbers> (multiple numbers, or single number with no matching plan) |
→ Read references/run.md and run those specific issues (no auto-chain — there's no sprint plan to base review/retro on) |
/sprint (no issues, no plan) |
→ Offer: "No sprint plan found. Run /sprint plan first, or pass issue numbers." |
/sprint review |
→ Read references/review.md |
/sprint retro |
→ Read references/retro.md |
Why auto-chain is the default: a sprint's post-run context (~300k+ tokens) is worth more than a single release cut. Running review and retro in a fresh /sprint review invocation pays a full cache miss to re-read everything you already know. Auto-chain executes review + retro inline in the same session and preserves it.
Disambiguation /sprint <N>: if .claude/sprints/sprint-<N>.md exists, <N> is a sprint number → auto-chain. Otherwise treat <N> as an issue number → run-only with no auto-chain.
Sprint numbering
Sprints are numbered sequentially. The current sprint number is determined by:
ls .claude/sprints/sprint-*.md | sort -t- -k2 -n | tail -1
If no sprint files exist, start at sprint 10 (we've done ~9 unnumbered sprints).
The sprint number threads through all phases:
- Plan writes
.claude/sprints/sprint-N.md - Run reads that file for its issue list
- Review appends results to that file
- Retro writes
.claude/diary/yyyyMMdd.N.md
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 75 lines · 69 tokens per session scan A 2699a50ee0ea
sprint is a skill published in the GitHub repository theshadow27/mcp-cli (2 stars, last pushed 5d ago), licensed MIT. It adds 69 tokens to every session and 1,366 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…