Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dmoskov/sharedskillsnpx agentmods add skills/dmoskov/sharedskills/task-decompositionWrote 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/dmoskov/sharedskills/task-decomposition)<a href="https://agentmods.dev/skills/dmoskov/sharedskills/task-decomposition"><img src="https://agentmods.dev/badge/skills/dmoskov/sharedskills/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/dmoskov/sharedskills/task-decomposition"><img src="https://agentmods.dev/badge/skills/dmoskov/sharedskills/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.00024 | $0.01219 |
| Opus 5.5 | $0.00010 | $0.00488 |
| Sonnet 5.5 | $0.00005 | $0.00244 |
| Haiku 4.5 | $0.00002 | $0.00122 |
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 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Decomposition Skill
Break large, module-level, or vague tasks into concrete file-level subtasks that agents (or humans) can execute independently. Each subtask targets specific files, has clear acceptance criteria, and is scoped to 30 min - 2 hr of work.
Subtasks are created as Asana subtasks of the parent task, with custom fields (execution status, effort, project, task type, validation status) populated from your workspace configuration — no GIDs are hardcoded in this skill.
Setup (one-time)
- Install the Asana client from this repo:
cd asana && ./setup.sh, setASANA_ACCESS_TOKEN - Create your workspace config:
Seepython3 asana/asana_config_loader.py template > ~/.config/ai-dev-tools/asana_config.yaml # Fill in your workspace's GIDs, then: python3 asana/asana_config_loader.py validateasana/asana_config.example.yamlfor a fully annotated example, including how to discover the GIDs for your workspace, projects, custom fields, and enum options. - To invoke this skill from other projects, symlink it into
~/.claude/skills/(or a project's.claude/skills/) and tell it where this repo lives:
Allln -s /path/to/ai-dev-tools/skills/task-decomposition ~/.claude/skills/task-decomposition export AI_DEV_TOOLS_DIR=/path/to/ai-dev-tools # add to your shell profileasana/...paths in this skill resolve against$AI_DEV_TOOLS_DIR(falling back to the current directory, which works when your session is inside this repo or a checkout that vendors it, e.g. as a git submodule).
When to Use
- A task touches multiple files or modules and is too broad for a single work session
- A task description is vague and needs concrete file targets before execution
- An XL or L effort task needs splitting into S/M subtasks
- A task has failed or timed out repeatedly — recurring failure usually means it's too large, not that execution keeps getting unlucky
Should You Decompose? (pre-flight checks)
What ships with it
1 file 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 · 119 lines · 24 tokens per session scan A 998dad6876f7
task-decomposition is a skill published in the GitHub repository dmoskov/sharedskills (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 1,219 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.
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,"…
remove
Remove a deployed framework or addon from the current workspace.