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-backlog-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-backlog-ado)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/audit-backlog-ado"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-backlog-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-backlog-ado"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-backlog-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.00119 | $0.01668 |
| Opus 5 | $0.00060 | $0.00834 |
| Sonnet 5 | $0.00024 | $0.00334 |
| Haiku 4.5 | $0.00012 | $0.00167 |
Grade A, and why
audit-backlog-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 10d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Audit — Azure DevOps
Purpose
A neglected backlog is a planning liability. Items without acceptance criteria become guesswork in Sprint Planning. Items that haven't moved in months crowd out real priorities. Items sized at 40 points can't be committed to. This audit surfaces all of it before it causes a problem, so the team walks into refinement with a clear picture of what needs attention.
Tool detection
This skill requires ADO MCP tools. If mcp__azure-devops__* tools are not active, tell the user: "This skill requires an Azure DevOps MCP connection. See docs/mcp-setup.md for setup instructions."
Step 1 — Identify the backlog scope
Ask: "Which project and team backlog should I audit? And how deep — just the top 20 items, the full backlog, or a specific number?"
Use wit_list_backlogs to confirm available backlog levels (Portfolio, Requirements, Task).
Default: audit the Requirements backlog (Product Backlog Items and Bugs) — the layer the team commits from. If the team uses a different backlog level, adjust.
Use wit_list_backlog_work_items or wit_query_by_wiql to retrieve the items. Sort by backlog rank (stack rank). Read: title, state, story points, description, acceptance criteria (custom field or description), tags, and last modified date.
Step 2 — Run the health checks
For each backlog item, evaluate the following criteria. Track counts and flag specifics.
2a — Readiness (Definition of Ready)
| Check | Pass condition | Flag if |
|---|---|---|
| Has a title | Clear, action-oriented | Title is "Story", "TBD", a jira key, or too vague to understand without context |
| Has a description or user story format | As a / I want / So that OR a clear description | Empty description |
| Has acceptance criteria | At least one testable AC | No acceptance criteria at all |
| ACs are testable | Each AC describes an observable condition | ACs are vague ("it should be good") or describe UI steps rather than outcomes |
| Has an estimate | Story points > 0 | Unestimated (null or 0) |
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.
- 10d ago First seen · 152 lines · 119 tokens per session scan A af98dbac65f9
audit-backlog-ado is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 119 tokens to every session and 1,668 once invoked, about $0.0006 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.