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 uthumany/uthy-legacy-os --skill epic-breakdowngit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/epic-breakdown)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/epic-breakdown"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/epic-breakdown/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/uthumany/uthy-legacy-os/epic-breakdown"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/epic-breakdown.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.00039 | $0.01211 |
| Opus 5.5 | $0.00016 | $0.00484 |
| Sonnet 5.5 | $0.00008 | $0.00242 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
epic-breakdown 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 2mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Breakdown
Overview
An epic is a story too large to fit in a sprint. The art of breaking it down is splitting it into stories that are independently valuable, small enough to complete in a sprint, and still solve the original problem. This skill covers Richard Lawrence's 9 patterns for splitting stories, plus techniques for managing epic-level requirements.
When to Use
- An epic is estimated at 2+ sprints of work
- Stories in the backlog feel too large to estimate
- You need to parallelize work across multiple developers or teams
- Stakeholders want to see incremental value, not wait for one big launch
- Don't use for: already-small stories (1-3 days of work), technical tasks that can't be split, or pure research
Instructions
1. Understand the Epic
Before splitting, understand the epic completely:
- Goal: What outcome does this epic serve?
- Scope: What's in and out of scope?
- User workflow: What's the end-to-end flow?
- Technical architecture: What are the natural seams in the system?
2. Apply Richard Lawrence's 9 Splitting Patterns
1. Workflow steps Split the epic by the steps in the user workflow. Each step becomes a story.
- Epic: "User can complete purchase" → Stories: Search → Add to cart → Checkout → Payment → Confirmation
2. Business rule variations Split by different rules or configurations.
- Epic: "Support multiple pricing plans" → Stories: Free plan → Pro plan → Enterprise plan
3. Input data variations Split by different types of input.
- Epic: "Import data" → Stories: Import from CSV → Import from JSON → Import from API
4. Operations (CRUD) Split by create, read, update, delete.
- Epic: "Team member management" → Stories: Add member → View members → Edit role → Remove member
5. Defer non-functional requirements Ship the functional behavior first, add performance/scalability later.
- Epic: "Search feature" → Stories: Basic search → Search indexing optimization → Search with faceted filters
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.
- 2mo ago First seen · 121 lines · 39 tokens per session scan A 6f4b452d57f9
epic-breakdown is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 1,211 once invoked, about $0.0002 per session on Opus 5.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.
epic-breakdown compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| epic-breakdownuthumany/uthy-legacy-os | Skill | 5 | 5mo ago | MIT | A | 39 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |