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/go1c/lumioagent/task-breakdownnpx skills add Go1c/LumioAgent --skill task-breakdowngit clone --depth 1 https://github.com/Go1c/LumioAgentWrote 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/go1c/lumioagent/task-breakdown)<a href="https://agentmods.dev/skills/go1c/lumioagent/task-breakdown"><img src="https://agentmods.dev/badge/skills/go1c/lumioagent/task-breakdown.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.00079 | $0.00877 |
| Opus 5 | $0.00039 | $0.00439 |
| Sonnet 5 | $0.00016 | $0.00175 |
| Haiku 4.5 | $0.00008 | $0.00088 |
Grade A, and why
task-breakdown 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 4d 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
Task Breakdown（任务拆解）
把一个模糊的大目标切成一组颗粒度合适、互不重叠、可独立完成的任务卡。每张卡都带验收标准，让执行者拿到就能动手，不必回头追问。
何时使用
- 拿到的目标太大或太模糊，无法直接开工。
- 一个目标涉及多个文件 / 模块 / 步骤。
- 需要把工作分派给不同执行者前，先理清边界和顺序。
操作步骤
- 澄清。 读目标 + 相关上下文（
AGENTS.md、knowledge/、相关源码），找出歧义和缺失信息；能从代码 / 文档确认的先确认，不能确认的明确列为待澄清项。 - 切分。 按「能独立完成且可独立验证」的原则切分。一个任务只解决一件事。
- 写卡。 按
.spec/tasks/README.md的格式契约写：一句话目标 / 涉及范围（文件集）/ 验收标准 / 依赖 + 可选「接口」节（Consumes / Produces）——字段口径以该契约为单一权威，此处不复述。有邻卡依赖的卡必须写接口契约（并行 worker 之间唯一的对齐依据），卡内禁占位符（判据见该契约）。深度计划（单功能、含完整代码与逐步验证）用writing-plans替代本技能。 - 排批。 标出任务间的依赖，划并行批次（wave）：同批内无依赖边且涉及文件集互不重叠；给出批序，批间串行（扇出规则见
AGENTS.md「并行边界与合入」）。 - 自检。 对照下方「验证」逐条确认。
快速参考
一张卡 = 一个 .spec/tasks/<slug>.md。字段定义与目录纪律的单一权威在 .spec/tasks/README.md，此处只给形状、不复述：
---
status: pending
---
# <一句话目标>
## 涉及范围
- <文件路径 1>
- <文件路径 2>
## 验收标准
- [ ] <可验证的条件 1>
- [ ] <可验证的条件 2>
## 依赖
无（或列前置卡 slug）
注意事项（Pitfalls）
- 别过度拆解。 能一步做完的事不要拆成多张卡。
- 验收标准必须可验证。 写「页面好看」不行，写「在移动端 375px 下无横向滚动」才行。
- 避免重叠。 两张卡改同一处逻辑，是该合并的信号。
- 待澄清项要显式列出，不要用猜测填空当成已知。
验证
- 每张卡都能让执行者不追问就开工。
- 每张卡的验收标准都可客观验证。
- 所有卡合起来正好覆盖原目标，无遗漏、无重叠、无超范围。
- 批次划分成立：同批任务无依赖边、文件集无重叠。
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.
- 4d ago First seen · 63 lines · 79 tokens per session scan A f48fb14b9dde
task-breakdown is a skill published in the GitHub repository Go1c/LumioAgent (20 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 877 once invoked, about $0.0004 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 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…