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 Mr-pixle/jira-mcp --skill sprint-reviewgit clone --depth 1 https://github.com/Mr-pixle/jira-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/mr-pixle/jira-mcp/sprint-review)<a href="https://agentmods.dev/skills/mr-pixle/jira-mcp/sprint-review"><img src="https://agentmods.dev/badge/skills/mr-pixle/jira-mcp/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/mr-pixle/jira-mcp/sprint-review"><img src="https://agentmods.dev/badge/skills/mr-pixle/jira-mcp/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.00096 | $0.01074 |
| Opus 5 | $0.00048 | $0.00537 |
| Sonnet 5 | $0.00019 | $0.00215 |
| Haiku 4.5 | $0.00010 | $0.00107 |
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 11d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Review Preparation
Keywords
sprint review, retrospective, retro, sprint demo, end of sprint, what did we finish, sprint wrap-up, close the sprint, unfinished work, carry over, بازبینی اسپرینت, رتروسپکتیو, پایان اسپرینت
Gather everything needed to run a sprint review, and turn "here is the data" into "here are the decisions you need to make".
This skill is read-only by default. It ends by proposing actions. Closing the sprint or moving issues happens only if the user explicitly asks, and those tools preview before applying.
Workflow
Step 1 — Identify the sprint
If the user named a board, find it with Board.list. If they named a project, list its boards and ask which one when there is more than one — do not guess, because a project with separate frontend and backend boards will give a misleading answer.
If they said "the current sprint", use Sprint.list with state="active".
Step 2 — Read the health
Run Report.sprint_health. This gives the verdict, the points and issue breakdown, the blockers, and the pace against elapsed time.
If it reports that no Story Points field exists, say so once and continue with issue counts. Do not silently present counts as if they were points.
Step 3 — Separate the unfinished work
Run Sprint.get_issues with jql='resolution = Unresolved' to get exactly what will not ship.
For each unfinished issue, work out which of these it is:
| Situation | Signal | Usual decision |
|---|---|---|
| Nearly done | In a late status, recently updated | Carry to next sprint |
| Blocked | Report.blocked_issues flags it |
Carry, but name what unblocks it |
| Never started | Still in a to-do status, no updates | Return to backlog — it was not really committed |
| Stalled | In progress, but untouched for days | Ask why; this is the interesting one |
To tell "stalled" from "in progress", run Report.blocked_issues with include_duration=true — days in current status is the signal.
Step 4 — Look for the pattern
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.
- 11d ago First seen · 96 lines · 96 tokens per session scan A 9d7862c19c60
sprint-review is a skill published in the GitHub repository Mr-pixle/jira-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,074 once invoked, about $0.0005 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.