task

A command for breaking work into small, trackable tasks and managing their status. It defines states such as pending, in progress, completed, and blocked.

In plain words
What is it for?
Use it to split features, integrations, and refactors into small units, set priorities, record blockers, check completion criteria, and choose the next task.
Why use it?
It makes large pieces of work easier to verify and reduces the chance of skipping dependencies or leaving unfinished work unrecorded.

Command

Install

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.

agentmods
npx agentmods add commands/xiaobei930/cc-best/task
Clone the repo
git clone --depth 1 https://github.com/xiaobei930/cc-best
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 701 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00701
Opus 5 $0.00005 $0.00351
Sonnet 5 $0.00002 $0.00140
Haiku 4.5 $0.00001 $0.00070

Measured 2d ago against content hash 21ab6b773e0c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

task 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.

commands/task.md · 93 lines

What it actually says

/task - 任务粒度管理

定义任务拆分标准和执行规范。

任务粒度标准

最小工作单元(原子任务)

定义: 不可再分的最小有意义操作

类型 示例 预期时间
创建文件 创建 api/routes.py 1-5 分钟
写单个函数 实现 process_data() 5-15 分钟
修复单个 bug 修复参数校验 5-30 分钟
添加单个测试 测试输入验证 5-10 分钟
更新配置 添加环境变量 1-5 分钟

复合任务(需拆分)

类型 拆分方式
集成模块 按接口 → 实现 → 测试
新功能 按数据层 → 逻辑层 → API 层
重构 按文件或按功能点

任务状态流转

待办 (pending)
  ↓ 开始执行
进行中 (in_progress)  ← 一次只能有一个
  ↓ 完成验证
已完成 (completed)

阻塞 (blocked) ← 遇到问题时
  ↓ 问题解决
回到进行中

执行规范

开始任务前

  1. 确认任务定义清晰
  2. 检查依赖是否就绪
  3. 标记任务为 in_progress

执行任务中

  1. 专注当前任务,不跳跃
  2. 遇到阻塞立即记录
  3. 小步验证,不累积

完成任务后

  1. 验证产出符合预期
  2. 更新任务状态为 completed
  3. 更新 progress.md
  4. 确定下一个任务

任务优先级

优先级 标识 含义
P0 阻塞其他任务 立即处理
P1 当前阶段必须完成 优先处理
P2 可以延后 正常处理
P3 可选优化 有空再做

任务拆分检查

好的任务拆分:

  • 每个任务有明确的完成标准
  • 每个任务可独立验证
  • 任务间依赖关系清晰
  • 单个任务不超过 30 分钟

需要继续拆分的信号:

  • 任务描述超过 2 行
  • 涉及多个文件的创建/修改
  • 无法在 30 分钟内完成
  • 完成标准模糊

记住: 任务管理的核心是可追踪——每个任务有状态、有完成标准,才能避免遗漏。

Changes

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.

  1. 2d ago First seen · 93 lines · 11 tokens per session scan A 21ab6b773e0c

Subscribe to this mod's changes

task is a command published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 701 once invoked, about $0.0001 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.