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 budagov-lab/DreamTeam --skill planner-task-decompositiongit clone --depth 1 https://github.com/budagov-lab/DreamTeamWrote 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/budagov-lab/dreamteam/planner-task-decomposition)<a href="https://agentmods.dev/skills/budagov-lab/dreamteam/planner-task-decomposition"><img src="https://agentmods.dev/badge/skills/budagov-lab/dreamteam/planner-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/budagov-lab/dreamteam/planner-task-decomposition"><img src="https://agentmods.dev/badge/skills/budagov-lab/dreamteam/planner-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.00032 | $0.00429 |
| Opus 5.5 | $0.00013 | $0.00172 |
| Sonnet 5.5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
planner-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.
What it actually says
Planner Task Decomposition
CRITICAL: Planner Delegates to Sub-Planner
Planner MUST NOT create task files directly. Planner creates epic outline, then dispatches Sub-Planner via mcp_task for each epic. Sub-Planner creates task files.
Left/Right: When you need planning, call planner (NOT planner-sub). Planner will call planner-sub per epic.
When to Use
- New goal or epic to implement
- User requests task breakdown or planning
- Meta Planner requests task resplitting
Workflow (Planner)
- Read context:
.dreamteam/memory/architecture.md,.dreamteam/memory/summaries.md - Break into epics — 5–50 blocks. Write
.dreamteam/docs/epics/[goal-slug].mdwith epic titles + short descriptions. - For each epic — mcp_task with
subagent_type: planner-sub, prompt:- "Expand epic N: [title + 5–10 line desc]. Create TXXX–TYYY. Dependencies: [Tprev]." (First epic: deps [].)
- After each Sub-Planner — Terminal:
python -m dreamteam sync-tasks - Return when all epics expanded. No task limit — system supports thousands of tasks.
What Sub-Planner Does (planner-sub)
- Reads epic + ID range from Planner prompt
- Creates task files in
.dreamteam/tasks/ - Returns "DONE. Created TXXX–TYYY (N tasks)."
Rules
- No circular dependencies
- Small tasks: 1–3 files per task, ~15–30 min each, single deliverable
- Dependencies must reference existing task IDs
- Planner never creates task_XXX.md — only Sub-Planner does
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 · 41 lines · 32 tokens per session scan A 14d64bf784f0
planner-task-decomposition is a skill published in the GitHub repository budagov-lab/DreamTeam (1 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 429 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.
planner-task-decomposition compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| planner-task-decompositionbudagov-lab/DreamTeam | Skill | 1 | 7mo ago | MIT | A | 32 | Cursor |
| nft-standardswshobson/agents | Skill | 42k | yesterday | MIT | A | 48 | Claude Code |
| linkerd-patternswshobson/agents | Skill | 42k | yesterday | MIT | A | 41 | Claude Code |
| postgresql-table-designwshobson/agents | Skill | 42k | yesterday | MIT | A | 37 | Claude Code |
| spark-training-gotchaswshobson/agents | Skill | 42k | yesterday | MIT | A | 63 | Claude Code |
| parallel-feature-developmentwshobson/agents | Skill | 42k | yesterday | MIT | A | 105 | Claude Code |
| cost-optimizationwshobson/agents | Skill | 42k | yesterday | MIT | A | 48 | Claude Code |