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/kopp0510/claude-dd/task-plannernpx skills add kopp0510/claude-dd --skill task-plannergit clone --depth 1 https://github.com/kopp0510/claude-ddWrote 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/kopp0510/claude-dd/task-planner)<a href="https://agentmods.dev/skills/kopp0510/claude-dd/task-planner"><img src="https://agentmods.dev/badge/skills/kopp0510/claude-dd/task-planner.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 | $0.00058 | $0.00909 |
| Opus 5 | $0.00029 | $0.00454 |
| Sonnet 5 | $0.00012 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
task-planner 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 today.
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
Task Planner — 微任務拆解
把設計拆成 2–5 分鐘的最小可執行任務，依賴排序，每個任務自包含（其他 agent 或新 session 不需額外查文件即可執行）。
輸入來源
依序找（存在的才讀）：
- 使用者指定的設計文件（如
docs/designs/*.md，design-brainstorm 的產物） - 舊 pipeline 的
claude_docs/（architecture / contracts / requirements，legacy 專案） - 都沒有 → 依使用者的口頭描述拆解，並把假設寫進計畫
拆解規則
粒度：一個資料模型 / API 端點 / 服務方法 / 前端組件 / 工具函數 = 1 個任務。 太大（多個不相關變更）→ 拆；太小（單行變更）→ 併；適當 = 一個可獨立驗證的功能單元。
依賴與排序：資料模型 → 服務層 → 控制器 → 路由；共用工具先於使用者；後端 API 先於 前端串接。拓撲排序，無依賴者在前，同層可並行。依賴不明確時採保守策略（假設有依賴）。
每個任務的格式：
#### 任務 N: <動詞開頭的任務名>
**檔案路徑：** <完整路徑>
**依賴：** 任務 X, Y（或「無」）
1. 寫失敗測試 — <測試檔路徑>、測什麼、關鍵測試碼
2. 驗證測試失敗 — <測試指令>
3. 實作 — <實作檔路徑>、關鍵邏輯
4. 驗證測試通過 — <測試指令>
5. 提交 — git add + commit（Conventional Commits）
產出
寫入 docs/plans/YYYY-MM-DD-<feature>.md（目錄不存在先建立）：
- 基本資訊：來源設計、總任務數
- 依賴圖（樹狀文字圖）
- 任務列表（上述格式）
- 段落分組：把任務依相依性分組為「功能段落」，每個段落對應一輪 8 步開發迴圈 （段落完成 = 迴圈跑完一圈：實作+測試 → commit → 簡化 → review → 再測 → commit）
產出前驗證（完成條件）
逐項核對，全過才算完成：
- 每個任務有檔案路徑、TDD 五步、依賴標註
- 依賴無循環；第一個任務零依賴；所有依賴都在計畫內
- 對照來源設計逐節檢查 — 每個模組 / 端點 / 組件都有對應任務，無遺漏
- 每個任務自包含（不需回查設計文件即可執行）
互動原則
不與使用者互動，直接產出計畫；來源不完整時在計畫中標註假設。產出後回報計畫路徑 與段落分組摘要，由使用者（或當前對話）決定何時開始第一個段落。
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.
- today Changed 641f81ce1aa2
- 4d ago First seen · 66 lines · 58 tokens per session scan A 7115025a7fb6
task-planner is a skill published in the GitHub repository kopp0510/claude-dd (6 stars, last pushed 4d ago), licensed MIT. It adds 58 tokens to every session and 909 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…