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-user-storygit 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-user-story)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/audit-user-story"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-user-story/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-user-story"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/audit-user-story.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.00135 | $0.01514 |
| Opus 5 | $0.00068 | $0.00757 |
| Sonnet 5 | $0.00027 | $0.00303 |
| Haiku 4.5 | $0.00014 | $0.00151 |
Grade A, and why
audit-user-story 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Story Audit
Purpose
A story that is unclear, too large, or untestable wastes the whole team's time — in refinement, in planning, and in delivery. This skill runs a structured audit so issues are caught before the story enters a Sprint, not during one.
Tool detection
- Check for active
mcp__azure-devops__*tools → set$PM_TOOLtoado - Otherwise check for active
mcp__jira__*tools → set$PM_TOOLtojira - If both → ask: "I see both ADO and Jira connected — which should I use?"
- If neither → set
$PM_TOOLtomanual
Step 1 — Fetch the story
- ADO / Jira: Ask: "What's the work item ID or issue key you'd like me to audit?" Then retrieve the full item including title, description, acceptance criteria, state, and any linked items.
- Manual: Ask the user to paste the story content directly.
Store the content as $STORY. If the item cannot be found, say so and ask the user to paste it instead.
Step 2 — Run the audit
Evaluate $STORY across four areas. Grade each check as:
- ✅ Pass — meets the standard
- ⚠️ Warning — present but weak; worth improving
- ❌ Fail — missing or clearly broken; blocks readiness
Area 1 — Story Format
| Check | Pass condition |
|---|---|
| Title is action-oriented | Starts with a verb + noun (e.g. "View monthly summary") |
| Story statement present | Has "As a / I want / So that" or equivalent |
| Persona is specific | Not "user", "the system", or "admin" |
| "So that" states value | Names an outcome or benefit, not a restatement of the want |
| No implementation detail in the story | Story describes what, not how |
Area 2 — Acceptance Criteria
| Check | Pass condition |
|---|---|
| ACs present | At least 3 criteria exist |
| ACs are conditions, not UI steps | Each AC describes an observable outcome, not a sequence of clicks |
| ACs are independently verifiable | Each AC can be tested without depending on another |
| Edge cases covered | Error states, empty states, or boundary conditions addressed where relevant |
| No ambiguous language | Avoid "should", "might", "fast", "easy" — prefer measurable specifics |
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 · 148 lines · 135 tokens per session scan A ded8126122a1
audit-user-story is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 135 tokens to every session and 1,514 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.