team

team is a command for Claude Code from bondarewicz/dreamteam. It costs 36 tokens per session (23,487 once invoked), scanned C, original, MIT.

A command that coordinates a full team of AI agents to solve a software problem. It assigns different roles for analysis, implementation, review, and final synthesis.

In plain words
What is it for?
Use it to coordinate multi-agent software work, prepare implementation plans, delegate coding and review, and combine the team's results.
Why use it?
It divides a large task among specialists so the work can be examined from several angles. The documented process also controls how code is planned, approved, and implemented.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions subagents; names the AskUserQuestion tool.

Not installable on its own: it runs a file from its repository that does not travel with it. Clone the repository, or install whatever ships that file. The line is bun evals/src/cli.ts --agent <name> --trials 3.

Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for team

README.md
[![agentmods](https://agentmods.dev/badge/commands/bondarewicz/dreamteam/team.svg)](https://agentmods.dev/commands/bondarewicz/dreamteam/team)
Your own site
<a href="https://agentmods.dev/commands/bondarewicz/dreamteam/team"><img src="https://agentmods.dev/badge/commands/bondarewicz/dreamteam/team.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 23,487 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.1 $0.00036 $0.23487
Opus 5 $0.00018 $0.11744
Sonnet 5 $0.00007 $0.04697
Haiku 4.5 $0.00004 $0.02349

Measured 5d ago against content hash 94568c86ca86, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade C, and why

team scanned grade C with 2 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 5d 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.

Subtle steeringmediumPrompt injection

Instructions that bias recommendations or shape behaviour without the user noticing.

**NEVER suggest the user push to production without completing this gate.** This is the single most important checkpoint in the entire workflow. A shipped bug costs 100x more than a caught one.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

DREAMTEAM_ROOT="$(cat "$HOME/.claude/dreamteam/repo-root" 2>/dev/null)"
commands/team.md · 2,029 lines

How it starts

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

You are Coach K, the Dream Team orchestrator. Your job is to coordinate the Dream Team agents to deliver results — from domain analysis through implementation, review, and synthesis.

Your coaching principles and decision rules are defined in your agent definition at ~/.claude/agents/coachk.md. Follow them in all decisions.

STEP 0: Workspace Setup

Initialize session variables once at the very start:

SESSION_WORKTREE=""
SESSION_BRANCH=""
REPO_ROOT="$(git rev-parse --show-toplevel)"

# Dream Team tooling repo — where eval templates and draft evals live.
# Resolved at install time (scripts/install.ts writes the path here) so /team
# can find the template and write drafts back to dreamteam regardless of which
# repo it is invoked in. Falls back to the working repo if not installed.
DREAMTEAM_ROOT="$(cat "$HOME/.claude/dreamteam/repo-root" 2>/dev/null)"
if [ -z "$DREAMTEAM_ROOT" ] || [ ! -d "$DREAMTEAM_ROOT" ]; then
  DREAMTEAM_ROOT="$REPO_ROOT"
fi
DRAFT_TEMPLATE="$DREAMTEAM_ROOT/evals/draft-template.md"

0a. Detect existing worktree context

GIT_COMMON=$(git rev-parse --git-common-dir 2>/dev/null)
GIT_DIR=$(git rev-parse --git-dir 2>/dev/null)

If GIT_COMMON != GIT_DIR, the user is already inside a worktree. Offer to reuse the current worktree or exit — do not create a nested one.

0b. Prune orphaned worktrees

Run git worktree prune silently to remove stale entries before checking for conflicts.

0c. Generate suggested branch name

Slugify $ARGUMENTS to form a branch name:

  • Lowercase, replace spaces and special characters with hyphens
  • Truncate slug at 50 characters
  • Append 4-char hash: first 4 characters of $(date +%s)$PPID | md5sum (or equivalent)
  • Pattern: team/<slug>-<4char-hash>

0d. Ask user for branch name

AskUserQuestion({
  questions: [{
    question: "Branch name for this session?",
    header: "Worktree",
    options: [
      { label: "<suggested-name>", description: "Use this branch name and create an isolated worktree" },
      { label: "Skip isolation", description: "Run in current directory without worktree (not recommended for concurrent sessions)" }
    ],
    multiSelect: false
  }]
})

Read the full file on GitHub · 2,029 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. 5d ago First seen · 2,029 lines · 36 tokens per session scan C 94568c86ca86

Subscribe to this mod's changes

team is a command published in the GitHub repository bondarewicz/dreamteam (1 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 23,487 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (subtle steering, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.