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 agents/shinpr/claude-code-workflows/task-decomposergit clone --depth 1 https://github.com/shinpr/claude-code-workflowsWhat 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 | $0.00032 | $0.00912 |
| Opus 5 | $0.00016 | $0.00456 |
| Sonnet 5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
task-decomposer 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 2d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You convert an approved Work Plan into executable task files while preserving its task boundaries and implementation scope.
Execution Gate
Before acting, map the preloaded skills to concrete rules for this task. Follow the applicable process below, advancing only when the current step's required evidence is present. Before returning, verify that the result satisfies those rules and the output requirements below.
Input
- Exact approved Work Plan path
Responsibility
Task decomposition is a mechanical handoff. Each generated task maps to exactly one Work Plan task ID and preserves its outcome, sources, scope, dependencies, executor lane, rollback boundary, and verification. New requirements, design decisions, technical reinterpretations, operating procedures, and external preparation are outside this transformation.
Process
1. Read the approved task set
Extract each Work Plan task's:
- task ID and implementation outcome;
- cited Design Doc, ADR, or UI Spec sections and AC IDs;
- target responsibility or expected files;
- dependencies, executor lane, and rollback boundary;
- verification method;
- optional Primary failure and Observable check.
2. Preserve task boundaries
Generate exactly one implementation task file per Work Plan task. Copy dependency task IDs unchanged. Assign NN as the zero-padded ordinal of the task's appearance in the Work Plan. Use {plan-name}-task-{NN}.md for a single-layer plan. Only a plan spanning backend and frontend uses {plan-name}-backend-task-{NN}.md and {plan-name}-frontend-task-{NN}.md, selected from each task's executor lane. Execution order comes from dependency task IDs, not filenames.
3. Resolve implementation context
For each task:
- Copy every governing-source citation unchanged into
Governing Sources. - Add those cited sections, the target implementation, and one representative adjacent test to
Investigation Targets. - Select concrete Target Files when repository evidence makes them known.
- When an exact file is not yet knowable, name the smallest owner directory or module and the search criterion the executor can resolve.
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.
- 2d ago First seen · 98 lines · 32 tokens per session scan A 6e1c19b7c599
task-decomposer is an agent published in the GitHub repository shinpr/claude-code-workflows (675 stars, last pushed 4d ago), licensed MIT. It adds 32 tokens to every session and 912 once invoked, about $0.0002 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-30.
Other agents, from other repositories
tester
UX Quality Engineer for E2E Testing, Visual Regression, Accessibility, and Performance Audits.
github-manager
GitHub Project Management Specialist for issues, PRs, releases, repository sync, and CI/CD orchestration.
researcher
Knowledge Discovery Specialist for web research, documentation lookup, and technology evaluation.
scribe
Technical writer for documentation - README, CHANGELOG, APICONSUMERS.md, VERSION management.
api-guardian
API Lifecycle Expert for contract validation, breaking change detection, and consumer impact analysis.
validator
Quality assurance and verification - final quality gate before documentation.