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 skills add Sprintra-io/sprintra-mcp --skill sprintra-sprint-reviewgit clone --depth 1 https://github.com/Sprintra-io/sprintra-mcpWrote 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/sprintra-io/sprintra-mcp/sprintra-sprint-review)<a href="https://agentmods.dev/skills/sprintra-io/sprintra-mcp/sprintra-sprint-review"><img src="https://agentmods.dev/badge/skills/sprintra-io/sprintra-mcp/sprintra-sprint-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sprintra-io/sprintra-mcp/sprintra-sprint-review"><img src="https://agentmods.dev/badge/skills/sprintra-io/sprintra-mcp/sprintra-sprint-review.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.00541 |
| Opus 5 | $0.00023 | $0.00270 |
| Sonnet 5 | $0.00009 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
sprint-review 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 12d 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
Sprint Review
Generate a comprehensive sprint review with metrics, story breakdown, and recommendations.
Process
Step 1: Load Sprint Data
sprints(method: "get_current")— current sprint + progress + readinessfeatures(method: "list")— all features (filter by sprint_id)ai(method: "get_next_work")— recommended priorities
Step 2: Calculate Metrics
From the sprint data, compute:
- Velocity: stories done / total stories (%)
- Points delivered: sum of completed story points
- Burndown status: on track / at risk / behind
- Readiness: how many stories are "ready" vs "needs_info" vs "not_ready"
Step 3: Format the Review
## Sprint Review: [sprint name]
### Progress
[done]/[total] stories ([percentage]%) | [points delivered]/[total points] SP
[=========> ] 55% complete
### By Status
- Done: [count] stories
- In Progress: [count] stories
- Todo: [count] stories
### Feature Breakdown
| Feature | Stories | Done | Status |
|---------|---------|------|--------|
| [name] | [total] | [done] | [on track / at risk] |
### Blockers & Risks
- [any stories stuck in in_progress for too long]
- [features with 0% progress]
- [dependencies not met]
### Recommendations
- [AI-recommended next work]
- [stories to deprioritize if sprint is at risk]
- [carry-over items for next sprint]
Step 4: If Sprint is Ending
If the user says "close the sprint" or "end sprint":
- Move incomplete stories to backlog or next sprint
sprints(method: "update", status: "completed")with retrospective data- Ask: "What went well? What to improve?" for the retro
Important
- Use tables and progress bars — make it scannable
- Flag risk early: if >50% time elapsed and <30% done, say so clearly
- Don't sugar-coat. Honest status is more valuable than optimistic status.
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.
- 12d ago First seen · 69 lines · 45 tokens per session scan A a41486835f46
sprint-review is a skill published in the GitHub repository Sprintra-io/sprintra-mcp (3 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 541 once invoked, about $0.0002 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
init-workspace-flow
Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
testgen-flow
Workflow for generating test cases from requirements (Issue Tracker / Wiki sources), exporting to a Test Management System, etc.
backlog
To validate story readiness for a sprint or to break work into a human WBS.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.