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-with-teamgit 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.00010 | $0.00229 |
| Opus 5 | $0.00005 | $0.00114 |
| Sonnet 5 | $0.00002 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
do-all-with-team 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.
What it actually says
Process all tasks in parallel using a team of agents and Claude Code's built-in task tools.
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
- Read the
builtin-tasks:team-leadskill for coordination guidelines - Call
TaskListto review all pending tasks and their dependencies - Create a team with
TeamCreate - Create tasks in the team's task list based on the pending built-in tasks
- Spawn team members using the
Tasktool, telling each to read thebuiltin-tasks:team-memberskill - Assign tasks to team members, respecting file overlap constraints from the team-lead skill
- Monitor progress, reassign tasks as members complete their work, and handle failures
- When all tasks are complete, shut down team members and clean up with
TeamDelete
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 · 26 lines · 10 tokens per session scan A ae445a61f512
do-all-with-team is a command published in the GitHub repository motlin/claude-code-plugins (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 10 tokens to every session and 229 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.
Other commands, from other repositories
multi-repo-swarm
Coordinate AI swarms across multiple repositories, enabling organization-wide automation and intelligent cross-project collaboration.
swarm-issue
Transform GitHub Issues into intelligent swarm tasks, enabling automatic task decomposition and agent coordination.
launch-worker
Manually launch headless workers against one or more GitHub issues.
polyphony-spawn
Create a new task in the Polyphony orchestrator and route it to an agent.
build-department
Use when an operator wants to create or refine a department, its head agent, intake posture, linked tools and workflows, and its role in the AI shadow department model.
swarms
Lists all active swarms working on the project, showing what each is working on and coordination opportunities.