team-spawn

A command for creating a team of coding agents from presets such as review, debugging, feature work, research, or security.

In plain words
What is it for?
Use it to start multi-agent code reviews, investigate bugs, develop features, or perform migrations and research.
Why use it?
It divides a larger task among agents with different responsibilities instead of handling every part in one process.

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/wshobson/agents/team-spawn
Clone the repo
git clone --depth 1 https://github.com/wshobson/agents
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,114 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.00025 $0.01114
Opus 5 $0.00013 $0.00557
Sonnet 5 $0.00005 $0.00223
Haiku 4.5 $0.00003 $0.00111

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

Security

Grade A, and why

team-spawn 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/agent-teams/commands/team-spawn.md · 107 lines

How it starts

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

Team Spawn

Spawn a multi-agent team using preset configurations or custom composition. Handles team creation, teammate spawning, and initial task setup.

Pre-flight Checks

  1. Verify that CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set:

    • If not set, inform the user: "Agent Teams requires the experimental feature flag. Set CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in your environment."
    • Stop execution if not enabled
  2. Parse arguments from $ARGUMENTS:

    • First positional arg: preset name or "custom"
    • --name: team name (default: auto-generated from preset)
    • --members N: override default member count
    • --delegate: enter delegation mode after spawning

Phase 1: Team Configuration

Preset Teams

If a preset is specified, use these configurations:

review — Multi-dimensional code review (default: 3 members)

  • Spawn 3 team-reviewer agents with dimensions: security, performance, architecture
  • Team name default: review-team

debug — Competing hypotheses debugging (default: 3 members)

  • Spawn 3 team-debugger agents, each assigned a different hypothesis
  • Team name default: debug-team

feature — Parallel feature development (default: 3 members)

  • Spawn 1 team-lead agent + 2 team-implementer agents
  • Team name default: feature-team

fullstack — Full-stack development (default: 4 members)

  • Spawn 1 team-implementer (frontend), 1 team-implementer (backend), 1 team-implementer (tests), 1 team-lead
  • Team name default: fullstack-team

research — Parallel codebase, web, and documentation research (default: 3 members)

  • Spawn 3 general-purpose agents, each assigned a different research question or area
  • Agents have access to codebase search (Grep, Glob, Read) and web search (WebSearch, WebFetch)
  • Team name default: research-team

security — Comprehensive security audit (default: 4 members)

  • Spawn 1 team-reviewer (OWASP/vulnerabilities), 1 team-reviewer (auth/access control), 1 team-reviewer (dependencies/supply chain), 1 team-reviewer (secrets/configuration)
  • Team name default: security-team

Read the full file on GitHub · 107 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 · 107 lines · 25 tokens per session scan A cf350aa8de37

Subscribe to this mod's changes

team-spawn is a command published in the GitHub repository wshobson/agents (39,318 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,114 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.