A guide to organizing and coordinating multiple coding agents on a software task. It explains when parallel work helps, how many agents to use, and how to divide responsibilities.

Use it to plan parallel code reviews, investigate unclear bugs, compare technical approaches, or split frontend, backend, and database work.

It helps teams decide when separate agents can work independently and reduces confusion when a task spans several parts of an application.

agent-teams — Skill for Claude Code by travisjneuman/.claude

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.

Any agent

npx skills add travisjneuman/.claude --skill agent-teams

Clone the repo

git clone --depth 1 https://github.com/travisjneuman/.claude

Made for: Claude Code.

Or install tjn-workflow, the plugin that ships this one along with the rest of its 9 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-teams/github.svg)](https://agentmods.dev/skills/travisjneuman/.claude/agent-teams)

Your own site

<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-teams"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-teams/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-teams"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-teams.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 667 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00038	$0.00667
Opus 5.5	$0.00015	$0.00267
Sonnet 5.5	$0.00008	$0.00133
Haiku 4.5	$0.00004	$0.00067

Measured 1mo ago against content hash 1eb2ac00d509, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-teams 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 1mo 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.

skills/agent-teams/SKILL.md · 83 lines

How it starts

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

Agent Teams Composition Skill

You have expertise in composing and orchestrating Claude Code Agent Teams. Use this knowledge when the user's task would benefit from parallel multi-session work.

Agent teams are off by default. Use them only when the user explicitly started the session with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1; otherwise use ordinary subagents, and don't propose teams unprompted.

When Agent Teams Fit

With teams enabled, they fit when:

The user asks for comprehensive code review (suggest 3-reviewer team)
The task involves work across multiple layers (frontend + backend + database)
The user describes a bug with unclear root cause (suggest competing hypothesis investigation)
The user wants to evaluate multiple technologies or approaches (suggest research panel)
The task can be clearly split into independent, file-separated workstreams

Do NOT suggest agent teams when:

The task is sequential or involves same-file edits
A single session or subagent would suffice
The coordination overhead would exceed the benefit
The user is on a tight token budget

Team Templates

Full Review (3 teammates)

Security reviewer + Performance reviewer + Correctness reviewer (edge cases, error paths, callers). Each reviews independently, then lead synthesizes findings.

Feature Dev (3 teammates)

Architect (plan approval required) + Implementer + Reviewer. Architect plans first, implementer follows, reviewer validates the diff by review.

Debug Squad (3-5 teammates)

Each teammate investigates a different hypothesis. Adversarial debate structure -- teammates challenge each other's theories.

Cross-Platform (3 teammates)

iOS developer + Android developer + Shared architect. Each platform teammate owns their own directory. Architect coordinates API contracts.

Full-Stack (3 teammates)

Frontend + Backend + Database. Clear file ownership per layer. Coordinate on API contracts first.

Research Panel (3 teammates)

Simplicity advocate + Performance advocate + Devil's advocate. Each evaluates from a different perspective, then synthesize.

Read the full file on GitHub · 83 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.

1mo ago Changed · +2 lines · +14 tokens per session 1eb2ac00d509
2mo ago First seen · 81 lines · 24 tokens per session scan A 8e38c53a7f71

Subscribe to this mod's changes

agent-teams is a skill published in the GitHub repository travisjneuman/.claude (108 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 667 once invoked, about $0.0002 per session on Opus 5.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-09-03.

Building agents Project management agents ai-coding ai-tools anthropic automation claude-ai

agent-teams next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
agent-teamstravisjneuman/.claude	Skill	108	yesterday	MIT	A	38	Claude Code
imagegenopenai/codex	Skill	135k	today	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	100k	today	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	316k	7d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code