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 commands/motlin/claude-code-plugins/do-all-tasksgit clone --depth 1 https://github.com/motlin/claude-code-pluginsWhat 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.00009 | $0.00490 |
| Opus 5 | $0.00005 | $0.00245 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
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.
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
- Track attempt count and previously attempted tasks to prevent infinite loops
- Call
TaskListto find the first pending, unblocked task - 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-taskagent 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-taskagent does this
- Verify HEAD tests good before the next task. After the
do-taskagent returns, rungit test run HEAD --retest --verbose --verbose(cached, so near-instant on an already-passing commit). If it does not return good (non-zero exit, orgit test results HEADreportsbad/unknown), stop the loop and report — do not stack the next task on a broken base. - Repeat until no incomplete tasks remain or the user's instructions are met
- When all tasks are completed, report the final status
Notes
- Each task is handled completely by the
do-taskagent before moving to the next - The
do-taskagent marks tasks as complete — do NOT callTaskUpdateyourself - Each task gets its own commit for clear history
- After each agent returns, call
TaskListagain 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"
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.
- 2d ago First seen · 48 lines · 9 tokens per session scan A be341384a00b
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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.