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-adogit 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-ado)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/audit-sprint-ado"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-sprint-ado/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-ado"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-sprint-ado.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.00145 | $0.01616 |
| Opus 5 | $0.00072 | $0.00808 |
| Sonnet 5 | $0.00029 | $0.00323 |
| Haiku 4.5 | $0.00015 | $0.00162 |
Grade A, and why
audit-sprint-ado 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADO Sprint Audit
Purpose
ADO gives teams enormous flexibility — which means it's easy to drift into habits that obscure progress, hide impediments, or make velocity data meaningless. This audit checks both Scrum health (is the team doing Scrum well?) and ADO hygiene (is the data in the board trustworthy?).
Prerequisites
This skill requires an active Azure DevOps MCP connection. If mcp__azure-devops__* or mcp__ado__* tools are not available, let the user know and stop.
Step 1 — Identify the sprint
Ask: "Which sprint should I audit — the current one, the one just completed, or a specific iteration path?"
Use work_list_team_iterations or work_list_iterations to confirm the iteration path. Store as $ITERATION.
Step 2 — Fetch sprint data
Retrieve all relevant data for $ITERATION:
- All work items in the iteration via
wit_get_work_items_for_iteration - Team capacity via
work_get_team_capacityorwork_get_iteration_capacities - Team settings (Definition of Done, working days) via
work_get_team_settings
Group items by type: PBI / User Story, Task, Bug, Test Case, 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 | Iteration has a non-empty goal field |
| Sprint Goal is outcome-oriented | Goal reads as a value statement, not a task list |
| All committed items relate to the Sprint Goal | No large clusters of work unrelated to the goal |
A missing Sprint Goal is a significant Scrum health issue — the team has no way to assess whether the Sprint was successful beyond counting items.
Area 2 — Work Item Hygiene (ADO)
| Check | Pass condition |
|---|---|
| All items have an assigned owner | No unassigned active or resolved items |
| All items are linked to the correct iteration | No stray items from other iterations |
| PBIs / User Stories have a parent (Feature or Epic) | Orphaned backlog items are harder to trace to strategy |
| Bugs are linked to the PBI they affect | Unlinked bugs obscure the root cause |
| No items in "Removed" state without a comment | Silent removals hide scope changes |
| Item titles are descriptive | No "New PBI", "Task 1", or copy-paste duplicates |
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 · 159 lines · 145 tokens per session scan A c980e431702e
audit-sprint-ado is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 145 tokens to every session and 1,616 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.