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 tqnonline/agent-forge --skill epic-decomposegit clone --depth 1 https://github.com/tqnonline/agent-forgeWrote 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/tqnonline/agent-forge/epic-decompose)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/epic-decompose"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/epic-decompose/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/tqnonline/agent-forge/epic-decompose"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/epic-decompose.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.00154 | $0.01343 |
| Opus 5.5 | $0.00062 | $0.00537 |
| Sonnet 5.5 | $0.00031 | $0.00269 |
| Haiku 4.5 | $0.00015 | $0.00134 |
Grade A, and why
epic-decompose 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Decomposition
Version: 1.0 | Role: Senior Product Manager (epic scoping and prioritization) Methodology: Detect > Extract > Validate > Approve > Output
You extract discrete epics from upstream artifacts or direct user input. Every epic must pass the DIVE test before it enters the manifest. Your output is a single epic manifest file that downstream skills -- primarily prd-draft -- consume to generate one PRD per epic.
Your core rule: no epic without DIVE validation. If an epic is not Deliverable, Independent, Valuable, and Estimable, it gets split or rejected.
Three Input Modes
| Mode | Name | Trigger | Input Artifacts |
|---|---|---|---|
| A | SaaS Pipeline | Understanding doc exists, no TOM | {project}/specs/{prefix}-understanding-doc.md |
| B | Consulting Pipeline | Understanding doc + TOM exist | Understanding doc + {project}/specs/tom/ artifacts |
| C | Standalone | No upstream artifacts found | Direct user input via AskUserQuestion |
Detection logic:
Globfor{project}/specs/*-understanding-doc.md-- if found, Mode A or BGlobfor{project}/specs/tom/-- if found, Mode B- If neither found, Mode C
Workflow
Step 1: Detect and Load
Mode A: Read understanding doc. Extract recommended epics, personas, process flows, initiative classification.
Mode B: Read understanding doc + TOM package. Extract TOM L1-L4 process taxonomy, maturity gaps, capability register, persona-role mappings. Group gaps by L1 process or system boundary.
Mode C: Use AskUserQuestion to gather business problem, target personas, key capabilities, constraints. Batch questions in groups of 2-3.
Load references: references/methodology/epic-decomposition.md
Step 2: Extract and Validate Epics
For each candidate epic, apply the DIVE test:
| Criterion | Test |
|---|---|
| Deliverable | Has a concrete, shippable outcome |
| Independent | Can be developed and released without other epics |
| Valuable | Delivers measurable value to at least one named persona |
| Estimable | Team can assign a rough effort range |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 118 lines · 154 tokens per session scan A dddc4b83dbba
epic-decompose is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 154 tokens to every session and 1,343 once invoked, about $0.0006 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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
dev-console-context
Use when the user mentions Developer Console, projects, workspaces, credentials, or orgs — or uses phrases like "show my projects", "list workspaces", "get credentials", "switch project", "which org", "my org", "console", "navigate", "explore", "what projects do I have", "show credentials", "what workspace". Also use…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.