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 agentmods add skills/ashermahonin/agentic-skills/decompose-worknpx skills add ashermahonin/agentic-skills --skill decompose-workgit clone --depth 1 https://github.com/ashermahonin/agentic-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/ashermahonin/agentic-skills/decompose-work)<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/decompose-work"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/decompose-work.svg" alt="Measured on agentmods" 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.00077 | $0.00419 |
| Opus 5 | $0.00039 | $0.00210 |
| Sonnet 5 | $0.00015 | $0.00084 |
| Haiku 4.5 | $0.00008 | $0.00042 |
Grade A, and why
decompose-work 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 6d 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.
What it actually says
Decompose Work
Purpose
Make implementation boring in the best way. Convert a big plan into small, owned, sequenced tasks that can run without stepping on each other.
Inputs
- Confirm requirements and architecture are approved enough to decompose.
- List deliverables and affected modules.
- Identify dependencies, shared files, contracts, and migration order.
- Decide which tasks can run in parallel and which must stay serial.
Decision process
- Create epics for coherent slices of value or infrastructure.
- Break epics into stories and tasks with clear done criteria.
- Assign each task a write scope, interfaces touched, validation command, and expected docs update.
- Build the dependency graph and critical path.
- Define parallel lanes only when file ownership and contracts are disjoint.
- Write merge order, conflict policy, and fallback if a lane blocks.
Decision boundaries
- Use Context7 MCP for current library, framework, platform, API, CLI, and configuration documentation whenever the task depends on external technology behavior.
Decision record
- Epics
- Stories
- Tasks
- Dependency graph
- Parallelization plan
- Agent role matrix
Ready when
- A task without validation is not ready.
- A parallel task without ownership boundaries is not parallel-ready.
- Do not split work by agent count; split by coherent boundaries.
- Keep merge order visible.
Handoff
Hand off each implementation task with scope, files, contracts, validation, docs, dependencies, and merge order.
References
references/parallelization-policy.md: Use this before running multiple agents or parallel implementation lanes.
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.
- 6d ago First seen · 55 lines · 77 tokens per session scan A 6b65bd1d969e
decompose-work is a skill published in the GitHub repository ashermahonin/agentic-skills (10 stars, last pushed 13d ago), licensed MIT. It adds 77 tokens to every session and 419 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.