next

A command that runs the next unfinished task from an implementation plan, while checking task dependencies and updating the work record.

In plain words
What is it for?
Use it to preview or check task status, run one specific task, execute the next ready task, or run independent tasks in parallel.
Why use it?
It removes the need to manually choose which planned task is ready and helps keep progress, tests, acceptance checks, and commits aligned with the plan.

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/stefan-jansen/claude-code-toolkit/next
Clone the repo
git clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkit
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 493 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.00008 $0.00493
Opus 5 $0.00004 $0.00246
Sonnet 5 $0.00002 $0.00099
Haiku 4.5 $0.00001 $0.00049

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

Security

Grade A, and why

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

plugins/workflow/commands/next.md · 64 lines

What it actually says

Execute Next Task

Execute pending tasks from .claude/work/ACTIVE_WORK work unit.

Arguments: $ARGUMENTS

Modes

  • --preview: List available tasks
  • --status: Show progress (completed/pending/blocked)
  • --task TASK-ID: Execute specific task
  • --parallel N: Execute N independent tasks concurrently
  • --parallel auto: Execute all independent tasks (max 5)
  • (no args): Execute next pending task

Process

  1. Load State: Read ACTIVE_WORK, verify state.json exists with status planning_complete or implementing

  2. Find Tasks: Query state.json for pending tasks with satisfied dependencies

  3. Execute:

    • Single task: Work directly on the task
    • Parallel: Launch Task agents concurrently (single message with multiple Task tool calls)
  4. Validate: Run tests, verify acceptance criteria met

  5. Update State: Mark task completed in state.json, update current_task

  6. Commit: Create atomic commit with task ID and description

Parallel Execution

For --parallel, find independent tasks (no unmet dependencies), launch as concurrent Task agents:

  • Each agent gets: task ID, title, description, acceptance criteria
  • Collect results, update state for each
  • Handle partial failures gracefully (some succeed, some fail)

State File Format

{
  "status": "implementing",
  "current_task": "TASK-003",
  "tasks": [
    {"id": "TASK-001", "title": "...", "status": "completed", "dependencies": []},
    {"id": "TASK-002", "title": "...", "status": "pending", "dependencies": ["TASK-001"]}
  ]
}

Error Handling

  • No active work unit → "Run /explore first"
  • No state.json → "Run /plan first"
  • All tasks blocked → Show blocked reasons
  • Partial parallel failure → Complete successful tasks, report failures
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 · 64 lines · 8 tokens per session scan A a9075f4c1a40

Subscribe to this mod's changes

next is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (85 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 493 once invoked, about $0.0000 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.