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 abrahamFerga/scrum-skills --skill audit-sprint-jiragit clone --depth 1 https://github.com/abrahamFerga/scrum-skillsWrote 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/abrahamferga/scrum-skills/audit-sprint-jira)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/audit-sprint-jira"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-sprint-jira/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/abrahamferga/scrum-skills/audit-sprint-jira"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-sprint-jira.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.00143 | $0.01747 |
| Opus 5 | $0.00072 | $0.00873 |
| Sonnet 5 | $0.00029 | $0.00349 |
| Haiku 4.5 | $0.00014 | $0.00175 |
Grade A, and why
audit-sprint-jira 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Sprint Audit
Purpose
Jira's flexibility is powerful and, unchecked, leads to boards where issues sit in the wrong state, story points are missing, epics are unlinked, and the Sprint Goal exists only in someone's memory. This audit checks both Scrum health and Jira hygiene so the team can trust their data and improve how they work.
Prerequisites
This skill requires an active Jira MCP connection. If mcp__jira__* tools are not available, let the user know and stop.
Step 1 — Identify the sprint
Ask: "Which sprint should I audit — the current active one, the most recently closed one, or a specific sprint by name?"
Use the available Jira sprint listing tool to confirm the sprint ID and name. Store as $SPRINT.
Step 2 — Fetch sprint data
Retrieve all issues in $SPRINT:
- All issues assigned to the sprint, including their type, status, story points, assignee, epic link, sub-tasks, and description/AC fields
- Sprint details including the Sprint Goal (if set)
Group issues by type: Story, Task, Bug, Sub-task, Epic, other.
Step 3 — Run the audit
Grade each check as:
- ✅ Pass — meets the standard
- ⚠️ Warning — worth improving
- ❌ Fail — missing or broken; impacts team effectiveness
Area 1 — Sprint Goal (Scrum)
| Check | Pass condition |
|---|---|
| Sprint Goal defined | Sprint has a non-empty goal field |
| Sprint Goal is outcome-oriented | Goal is a value statement, not a task list or feature dump |
| Committed issues relate to the Sprint Goal | No large clusters of work that don't connect to the goal |
A missing Sprint Goal means the team cannot assess whether the Sprint succeeded — it reduces the Sprint to a time-boxed to-do list.
Area 2 — Issue Hygiene (Jira)
| Check | Pass condition |
|---|---|
| All issues have an assignee | No unassigned In Progress or Done issues |
| Stories are linked to an Epic | Unlinked stories are harder to track against the Product Goal |
| Bugs are linked to the story they affect | Unlinked bugs obscure cause and context |
| Issue titles are descriptive | No "Story 1", "Bug", or untitled issues |
| No duplicate issues | Check for titles that are near-identical |
| Issue types used correctly | No Stories filed as Tasks or Bugs filed as Stories |
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 · 169 lines · 143 tokens per session scan A 645fae9f2efe
audit-sprint-jira is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 143 tokens to every session and 1,747 once invoked, about $0.0007 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
turborepo
Skill "turborepo" from ashish7802/awesome-api-skills, covering turborepo skill, ecosystem graph preview, recommended next skills, quick start and production patterns.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
devflow-planning
AI-powered sprint planning, velocity analysis, and capacity forecasting. Use for planning sprints, predicting outcomes, and providing agile recommendations based on historical data.
git-jira-integration
Integration between Git workflows and Jira issues. Generates branch names from issues, validates commit messages, and provides PR context from Jira specifications.