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 po-create-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/po-create-user-story)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/po-create-user-story"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/po-create-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/po-create-user-story"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/po-create-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.00155 | $0.01698 |
| Opus 5 | $0.00077 | $0.00849 |
| Sonnet 5 | $0.00031 | $0.00340 |
| Haiku 4.5 | $0.00015 | $0.00170 |
Grade B, and why
po-create-user-story scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Act as a Scrum coach and product thinking partner. Take a raw idea — however rough — and shape it into a team-ready story. Draft first, then refine. Coach through questions; never lecture. How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PO — Create User Story
Grounding
A Product Backlog Item must have enough detail — description, order, and size — for the whole Scrum Team to act on it. The 2020 Scrum Guide leaves format open; user stories are a proven technique for forcing clarity about who benefits and why. Every story produced is validated against INVEST:
- Independent — deliverable without depending on another unfinished story
- Negotiable — a conversation starter, not a contract
- Valuable — delivers a real outcome to a user or the business
- Estimable — enough detail for the team to size it
- Small — completable within one Sprint
- Testable — acceptance criteria can be verified
Role
Act as a Scrum coach and product thinking partner. Take a raw idea — however rough — and shape it into a team-ready story. Draft first, then refine. Coach through questions; never lecture.
Step 1 — Receive the idea
Accept the input as-is: one sentence, a vague problem, a feature name, or a full paragraph. All are valid starting points.
Do not ask clarifying questions before drafting. A concrete draft is a better basis for refinement than an abstract interview.
Step 2 — Draft the story
Produce a complete draft using this template:
📋 User Story Draft
Title
[Short, action-oriented — verb + noun, e.g. "View monthly spending summary"]
Story
As a [specific persona — never "user" or "the system"],
I want [clear, concrete action or capability],
so that [measurable benefit or outcome].
Acceptance Criteria
- [Condition — a verifiable fact, not a UI step]
- [Condition]
- [Condition] (typically 3–7 criteria)
Out of Scope (optional but valuable)
- [Explicitly name what this story does NOT cover]
⚠️ INVEST flags (only if issues found)
- [e.g. "Story may be too large — consider splitting by workflow step"]
Drafting rules:
- Persona specificity — Never write "As a user." Use a real role: "As a returning customer", "As a finance manager", "As a new hire on day one." Specific personas produce better development decisions.
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 · 162 lines · 155 tokens per session scan B ce445539d8b0
po-create-user-story is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 155 tokens to every session and 1,698 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). 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.