task

A command for planning and carrying out complex coding tasks. It can break work into smaller pieces and delegate independent pieces to multiple subagents, meaning separate coding assistants working on assigned parts.

In plain words
What is it for?
Use it for multi-step features, work that can be split across files or areas, delegated tasks, or projects that need saved progress.
Why use it?
It provides structure for large or long-running work and can run suitable parts in parallel instead of handling everything as one sequence.

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/drag88/claude-dev-framework/task
Clone the repo
git clone --depth 1 https://github.com/drag88/claude-dev-framework
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 862 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.00012 $0.00862
Opus 5 $0.00006 $0.00431
Sonnet 5 $0.00002 $0.00172
Haiku 4.5 $0.00001 $0.00086

Measured yesterday against content hash 32c547809655, 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 yesterday.

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 · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/cdf:task — Task Execution

Execute defined tasks with structured delegation when fan-out is warranted. For multi-step work, write a clear prompt and let Claude plan — orchestration scaffolding has been removed in favor of native planning.

Quick Start

/cdf:task create "enterprise authentication system"
/cdf:task execute "feature backlog" --delegate --parallel
/cdf:task --breakdown "implement user authentication system"

When to Use

  • Task requires fan-out across multiple subagents working in parallel
  • You want a documented delegation contract (tools whitelist + scope boundaries) for each subagent
  • Long-running work where state persistence matters

For single-subagent work or simple sequential steps, just write the prompt — Claude plans that well from a clear prompt at high effort.

Delegation contract (when fanning out)

When invoking the Task tool, include these seven sections so the subagent has everything it needs in one turn:

### 1. Task
Atomic, specific goal — one action only.

### 2. Expected outcome
Concrete deliverables with measurable success criteria.

### 3. Required skills
Which CDF skill or agent to invoke (e.g. "codebase-navigator", "library-researcher").

### 4. Required tools
Explicit tool whitelist (e.g. "Read, Grep, Glob"). No tools outside this list.

### 5. Required actions
- Each requirement on its own line
- Be specific and actionable
- Reference real file paths and patterns

### 6. Out of scope
- Forbidden actions
- Scope boundaries
- Quality constraints

### 7. Context
- File paths: relevant paths
- Patterns: naming conventions, code patterns
- Constraints: time, scope, dependencies

Skeleton

### 1. Task
<one atomic goal>

### 2. Expected outcome
<deliverables and success criteria>

### 3. Required skills
<skill or agent name>

### 4. Required tools
<explicit tool whitelist>

### 5. Required actions
<one requirement per line>

### 6. Out of scope
<forbidden actions and boundaries>

### 7. Context
<file paths, patterns, constraints>

Read the full file on GitHub · 119 lines

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. yesterday First seen · 119 lines · 12 tokens per session scan A 32c547809655

Subscribe to this mod's changes

task is a command published in the GitHub repository drag88/claude-dev-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 862 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-31.