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-split-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-split-story)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/po-split-story"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/po-split-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-split-story"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/po-split-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.00113 | $0.01753 |
| Opus 5 | $0.00056 | $0.00877 |
| Sonnet 5 | $0.00023 | $0.00351 |
| Haiku 4.5 | $0.00011 | $0.00175 |
Grade A, and why
po-split-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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Splitting
Purpose
A story that cannot fit in one Sprint is a planning liability — it blocks commitment, obscures progress, and almost always hides scope nobody agreed to. This skill applies the nine proven splitting patterns to turn one large story into multiple small ones, each independently valuable and completable in a single Sprint.
Tool detection
- Check for active
mcp__azure-devops__*tools →$PM_TOOL = ado - Check for active
mcp__jira__*tools →$PM_TOOL = jira - If both → ask which tool to use
- If neither →
$PM_TOOL = manual
Step 1 — Fetch the story
Ask: "Which story needs splitting? Provide the ID or paste the content."
- ADO: use
wit_get_work_item— read title, description, acceptance criteria, story points, and parent - Jira: use the get-issue tool — read summary, description, acceptance criteria, story points, and epic link
- Manual: accept pasted content
If the item is an Epic, treat the whole Epic as the input. Store as $STORY.
Step 2 — Diagnose why it is too large
Before splitting, understand what makes it large. This determines which pattern fits best.
Ask yourself — and the PO if needed:
- Does it cover multiple user types? → split by persona
- Does it span multiple workflow steps end-to-end? → split by workflow
- Does it handle many data variations or edge cases? → split by data
- Does it cover both the happy path and error handling? → split happy/unhappy
- Does it need to work across multiple channels (web, mobile, API)? → split by interface
- Does it include both basic and high-performance versions? → split by performance
- Does it bundle create, read, update, delete? → split by operation (CRUD)
- Does it mix a core feature with validation, logging, or notifications? → split cross-cutting concerns
- Does it depend on a system integration that is not ready? → defer the integration, stub it first
Step 3 — Apply the best-fit pattern
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 · 214 lines · 113 tokens per session scan A 93c877470d84
po-split-story is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 113 tokens to every session and 1,753 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.