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 skills/wittyreference/twilio-claude-plugin/agent-teams-guidenpx skills add wittyreference/twilio-claude-plugin --skill agent-teams-guidegit clone --depth 1 https://github.com/wittyreference/twilio-claude-pluginWrote 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/wittyreference/twilio-claude-plugin/agent-teams-guide)<a href="https://agentmods.dev/skills/wittyreference/twilio-claude-plugin/agent-teams-guide"><img src="https://agentmods.dev/badge/skills/wittyreference/twilio-claude-plugin/agent-teams-guide.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00014 | $0.00577 |
| Opus 5 | $0.00007 | $0.00289 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
agent-teams-guide 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 4d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: agent-teams-guide description: Reference for agent team configurations and coordination. Use when launching /team, understanding teammate communication, or choosing between parallel workflows (new-feature, bug-fix, code-review, refactor, docs-update).
Agent Teams Guide
Agent Teams (experimental) coordinate multiple Claude Code instances for parallel work. Each teammate gets its own context window and can communicate via direct messaging and a shared task list.
How to Use
/team new-feature "Add SMS verification"
/team bug-fix "webhook returning 500 for empty body"
/team code-review functions/voice/
/team refactor functions/helpers/
Configurations
| Team | Structure | Best For |
|---|---|---|
new-feature |
Sequential build → parallel qa + review → docs | Complex features |
bug-fix |
3 parallel investigators → fix → verify | Debugging |
code-review |
3 parallel reviewers → cross-challenge | Thorough review |
refactor |
Parallel analysis → implement → parallel verify | Restructuring |
docs-update |
Parallel blind writers → parallel multi-lens reviewers → final editor | Batch doc fixes, doc-gap remediation |
validation |
Parallel domain validators → lead synthesizes | Post-deploy E2E verification |
Key Characteristics
- Lead operates in delegate mode (coordination only, no direct coding)
- Quality gates enforced via
TeammateIdleandTaskCompletedhooks - Teammates share findings via messaging — not just results flowing one direction
- ~2-3x token cost vs subagents — use for high-value tasks
When to Use Teams vs Subagents
| Criteria | Use Sequential Phases | Use Teams (/team) |
|---|---|---|
| Task structure | Sequential, clear phases | Parallel or adversarial |
| Communication | Results flow one direction | Agents discuss findings |
| Context needs | Shared context is fine | Each agent needs fresh context |
| Token budget | Tight | Flexible (2-3x more) |
| Best for | Routine features | Bug debugging, code review, complex features |
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.
- 4d ago First seen · 65 lines · 14 tokens per session scan A 1c49390225cc
agent-teams-guide is a skill published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 577 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…