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 skills add DmitriyYukhanov/claude-plugins --skill agent-teamsgit clone --depth 1 https://github.com/DmitriyYukhanov/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/dmitriyyukhanov/claude-plugins/agent-teams)<a href="https://agentmods.dev/skills/dmitriyyukhanov/claude-plugins/agent-teams"><img src="https://agentmods.dev/badge/skills/dmitriyyukhanov/claude-plugins/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.
<a href="https://agentmods.dev/skills/dmitriyyukhanov/claude-plugins/agent-teams"><img src="https://agentmods.dev/badge/skills/dmitriyyukhanov/claude-plugins/agent-teams.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00151 | $0.01358 |
| Opus 5.5 | $0.00060 | $0.00543 |
| Sonnet 5.5 | $0.00030 | $0.00272 |
| Haiku 4.5 | $0.00015 | $0.00136 |
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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Teams
Coordinate multiple Claude Code instances working together. One session acts as team lead, spawning and coordinating teammates that work independently in their own context windows and communicate directly with each other.
Quick Setup
1. Enable the feature (experimental, disabled by default)
Add to settings.json:
{
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
}
}
Or set the environment variable directly:
export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
2. Start a team
Tell Claude to create an agent team with a natural language prompt describing the task and team structure:
Create an agent team to review PR #142. Spawn three reviewers:
- One focused on security implications
- One checking performance impact
- One validating test coverage
Claude creates the team, spawns teammates, coordinates work, and synthesizes results.
When to Use Agent Teams vs Subagents
| Criteria | Use Subagents | Use Agent Teams |
|---|---|---|
| Workers need to talk to each other | No | Yes |
| Task is focused, result-only matters | Yes | No |
| Complex work requiring discussion | No | Yes |
| Token budget is tight | Yes (lower cost) | No (higher cost) |
| Workers need shared task list | No | Yes |
Best use cases for agent teams:
- Research and review: parallel investigation of different aspects
- New modules/features: each teammate owns a separate piece
- Debugging competing hypotheses: test theories in parallel
- Cross-layer coordination: frontend, backend, and tests each owned by different teammates
Display Modes
Two modes available. Set in settings.json or via CLI flag.
In-process (default fallback): All teammates in your main terminal.
Shift+Up/Downto select a teammateEnterto view a teammate's session,Escapeto interruptCtrl+Tto toggle task list
Split panes: Each teammate gets its own pane (requires tmux or iTerm2).
- Click into a pane to interact directly
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 182 lines · 151 tokens per session scan A 0fd893ecfd2e
agent-teams is a skill published in the GitHub repository DmitriyYukhanov/claude-plugins (8 stars, last pushed 14d ago), licensed MIT. It adds 151 tokens to every session and 1,358 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
branch-recap
Takes stock of what a branch actually changed, before it gets pushed — works out the scope itself, then lays the change out group by group in one pass: files touched, what was done and why, how, and what deserves a second look, quoting code only where a remark needs it rather than reprinting the diffs. Closes on a…
audit-context
Measures where a project's Claude context is going before applying any of clean-context's levers. Reports what Glob discovers with and without ignore files applied, the twenty largest files in the repo and which are generated, the cumulative size of every CLAUDE.md loaded for this working directory, and how many MCP…
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read: filtered to what they would actually notice, one bullet per idea, plain language, no code vocabulary. Works out the scope itself across however many repositories sit in the working directory (a project can span several…
ignore-setup
Set up a project so Claude stops discovering lockfiles, generated code, minified assets and binaries on every search — a managed .ignore, the Glob setting that makes Glob obey it, and a short read-deny list for secrets. Use when someone asks for a .claudeignore, asks to exclude files from the context, says Claude…
access
Manage who may drive telegram-topics sessions — view and edit the user allowlist. Use when the user asks to allow or remove a Telegram user, check who's allowed, or lock the channel down.
code-standards
Prabhdeep (Sonu) Singh's personal coding standards — the house rules and quality bar for how code gets written. INVOKE before writing, generating, refactoring, or reviewing ANY code in ANY language — schemas, endpoints, queries, logging, validation, error handling — even when nobody says "standards" or "style".…