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 aigentive/RalphX --skill task-decompositiongit clone --depth 1 https://github.com/aigentive/RalphXWrote 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/aigentive/ralphx/task-decomposition)<a href="https://agentmods.dev/skills/aigentive/ralphx/task-decomposition"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/task-decomposition/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/aigentive/ralphx/task-decomposition"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/task-decomposition.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.00014 | $0.01280 |
| Opus 5.5 | $0.00006 | $0.00512 |
| Sonnet 5.5 | $0.00003 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
task-decomposition 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 1mo 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Decomposition Skill
This skill helps break down complex features into atomic, independently implementable tasks.
Core Principles
1. Right-Sized Tasks
Each task should be:
- Completable in 1-4 hours of focused work
- Independently testable
- Shippable on its own (even if feature is incomplete)
- Clear enough that someone else could pick it up
2. Vertical Slices
Prefer vertical slices over horizontal layers:
Good (Vertical):
- "Add login button that shows login modal"
- "Implement password validation on login form"
- "Add remember me checkbox to login"
Avoid (Horizontal):
- "Create all auth UI components"
- "Write all auth business logic"
- "Add all auth tests"
3. Dependency Minimization
Order tasks to minimize blocking:
- Foundation tasks (types, interfaces, infrastructure)
- Core functionality (main features)
- Enhancements (polish, edge cases)
- Integration (connecting pieces)
Decomposition Patterns
Pattern: Feature -> Tasks
Feature: "Dark mode support" Decomposition:
- Define color tokens (CSS variables)
- Create theme context
- Add theme toggle component
- Update navigation to use theme colors
- Update cards to use theme colors
- Update modals to use theme colors
- Persist theme preference
- Detect system preference
Pattern: CRUD -> Tasks
Feature: "Task comments" Decomposition:
- Add comments field to task entity
- Create comment repository
- Add create comment command
- Add list comments command
- Create comment list component
- Create comment input component
- Integrate comments into task detail view
Pattern: Integration -> Tasks
Feature: "Connect to external API" Decomposition:
- Define API response types
- Create API client module
- Implement authentication
- Add fetch method for resource
- Create loading states
- Add error handling
- Implement retry logic
- Add caching layer
Pattern: Targeted Testing
Every plan decomposition MUST include a testing strategy that scales with the implementation — not blanket full-suite runs at every gate.
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.
- 1mo ago First seen · 177 lines · 14 tokens per session scan A 1ea4b1830be9
task-decomposition is a skill published in the GitHub repository aigentive/RalphX (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,280 once invoked, about $0.0001 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.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…