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 christopherlouet/claude-base --skill agent-teamsgit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/agent-teams)<a href="https://agentmods.dev/skills/christopherlouet/claude-base/agent-teams"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/agent-teams.svg" alt="Measured on agentmods" 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.00039 | $0.02106 |
| Opus 5 | $0.00019 | $0.01053 |
| Sonnet 5 | $0.00008 | $0.00421 |
| Haiku 4.5 | $0.00004 | $0.00211 |
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 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Teams (Multi-Agent Orchestration)
Coordinate multiple Claude Code instances working together as a team, with shared tasks, inter-agent messaging, and centralized management.
Prerequisites
- Claude Code >= 2.1.19
- Feature flag enabled:
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS - tmux (optional): for split-panes mode
Activation
Add to .claude/settings.local.json or .claude/settings.json:
{
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
}
}
Or via environment variable:
export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
When to use Agent Teams vs Sub-Agents
┌────────────────────────────────────────────────────────────────────┐
│ AGENT TEAMS vs SUB-AGENTS: DECISION GUIDE │
├────────────────────────────────────────────────────────────────────┤
│ │
│ AGENT TEAMS if: │
│ - Agents need to COMMUNICATE with each other │
│ - COMPLEX work requiring discussion and collaboration │
│ - Tasks with coordination (cross-review, debate, consensus) │
│ - 3+ agents working in parallel over a long duration │
│ │
│ SUB-AGENTS (Task tool) if: │
│ - FOCUSED task where only the result matters │
│ - No need for inter-agent communication │
│ - 1-2 agents for short tasks │
│ - Token economy is the priority │
│ │
│ MANUAL PARALLEL SESSIONS (git worktrees) if: │
│ - Full control over each session │
│ - No need for automatic coordination │
│ - Work on completely independent branches │
│ │
└────────────────────────────────────────────────────────────────────┘
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.
- 4d ago First seen · 187 lines · 39 tokens per session scan A c8cd94098664
agent-teams is a skill published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 2,106 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
tmux-layout
Use this skill when the operator wants a prepared tmux visualization layout for the session's side-channels (STATE.md tail, CI-watch, events.jsonl tail). Renders a 4-pane default layout or debug layout. Read-only side-channel observability — the coordinator chat stays in the operator's original terminal. Trigger…
Gmail
Read, search, send, and manage emails via Gmail API. Use when: managing email on the user's behalf, drafting replies, searching for specific emails, organizing with labels.
Notion
Search, read, create, and manage Notion pages and databases.
Scheduler
Create and manage scheduled tasks with cron, interval, or one-time execution.
Slack
Search messages, manage channels, reactions, pins, and users in Slack.
memstack-automation-n8n-workflow-builder
Use this skill when the user says 'n8n workflow', 'build a workflow', 'automation workflow', 'connect services', or needs visual workflow design with node mapping, data transformations, and error handling for n8n. Do NOT use for standalone webhook endpoints or cron jobs.