do-all-tasks

A command that repeatedly works through incomplete items in the coding assistant's built-in task list. It gives each task to a task-working agent and checks the current commit's tests before continuing.

In plain words
What is it for?
Use it to process all pending, unblocked tasks automatically, limit repeated attempts on the same task, and verify each completed task before moving on.
Why use it?
It reduces manual task switching and stops when a task cannot be completed safely or the latest code fails its checks.

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/motlin/claude-code-plugins/do-all-tasks
Clone the repo
git clone --depth 1 https://github.com/motlin/claude-code-plugins
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 490 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.00009 $0.00490
Opus 5 $0.00005 $0.00245
Sonnet 5 $0.00002 $0.00098
Haiku 4.5 $0.00001 $0.00049

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

Security

Grade A, and why

do-all-tasks 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/builtin-tasks/commands/do-all-tasks.md · 48 lines

How it starts

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

Process all tasks automatically using Claude Code's built-in task tools.

Repeatedly work through incomplete tasks from the built-in task list.

If the user provided additional instructions, they will appear here:

If the user did not provide instructions, work through ALL incomplete tasks until NONE remain.

Steps

  1. Track attempt count and previously attempted tasks to prevent infinite loops
  2. Call TaskList to find the first pending, unblocked task
  3. If a task is found:
    • Check if we have already attempted this task 1 time
    • If yes, skip it and continue to the next task
    • If no, launch the builtin-tasks:do-task agent to implement it
    • Do NOT add instructions to the agent prompt — the agent is self-contained and follows its own workflow (including precommit, commit, rebase)
    • Do NOT mark the task as complete yourself — the do-task agent does this
  4. Verify HEAD tests good before the next task. After the do-task agent returns, run git test run HEAD --retest --verbose --verbose (cached, so near-instant on an already-passing commit). If it does not return good (non-zero exit, or git test results HEAD reports bad/unknown), stop the loop and report — do not stack the next task on a broken base.
  5. Repeat until no incomplete tasks remain or the user's instructions are met
  6. When all tasks are completed, report the final status

Notes

  • Each task is handled completely by the do-task agent before moving to the next
  • The do-task agent marks tasks as complete — do NOT call TaskUpdate yourself
  • Each task gets its own commit for clear history
  • After each agent returns, call TaskList again to see if more tasks remain

User feedback

Throughout the process, provide clear status updates:

  • "Starting task: [task subject]"
  • "Task completed successfully: [task subject]"
  • "Task failed: [task subject]"
  • "Skipping previously failed task: [task subject]"
  • "All tasks completed" or "Stopping due to failures"

Read the full file on GitHub · 48 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. 2d ago First seen · 48 lines · 9 tokens per session scan A be341384a00b

Subscribe to this mod's changes

do-all-tasks is a command published in the GitHub repository motlin/claude-code-plugins (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 9 tokens to every session and 490 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.