Borrowing it
Nothing to install: this file belongs to robconery/kolea. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/robconery/kolea/main/.claude/skills/agent-teams/SKILL.mdgit clone --depth 1 https://github.com/robconery/koleaWrote 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/robconery/kolea/agent-teams)<a href="https://agentmods.dev/skills/robconery/kolea/agent-teams"><img src="https://agentmods.dev/badge/skills/robconery/kolea/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/robconery/kolea/agent-teams"><img src="https://agentmods.dev/badge/skills/robconery/kolea/agent-teams.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00161 | $0.01520 |
| Opus 5.5 | $0.00064 | $0.00608 |
| Sonnet 5.5 | $0.00032 | $0.00304 |
| Haiku 4.5 | $0.00016 | $0.00152 |
Grade A, and why
agent-teams scanned grade A with 1 finding 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 2mo 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
// ~/.claude/settings.json Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Copies of this mod
2 near-identical copies found in the catalogue:
- agent-teams — 100% identical, 0 lines differ
- agent-teams — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Teams orchestration
Claude Code's experimental Agent Teams coordinates multiple Claude Code sessions. The session that creates the team is the lead (you, here); teammates are separate sessions with their own full context windows that message each other directly and pull work off a shared task list.
This differs from subagents (the Agent tool): subagents run inside one
session and only report back to their parent. Teammates are peers — they
coordinate through a shared mailbox and task list, and self-claim work.
The one rule this skill exists to enforce
Delegate and wait. Do not implement the parallel work yourself in the lead session. When a task decomposes into independent streams, the lead's job is to spawn teammates, assign/seed tasks, monitor, and synthesize — not to write module A then module B then the tests sequentially. If you catch yourself doing the work, stop and delegate it.
- ❌ Anti-pattern: "Write the auth module, then the API, then the tests" → lead does all three in order.
- ✅ Pattern: spawn 3 teammates (auth / API / tests), assign clear tasks, then wait for all to finish before synthesizing.
If asked to proceed and teammates aren't done: do not start doing their work — wait, or steer them.
Preflight — is it enabled?
Agent Teams is off by default and needs Claude Code v2.1.32+. It
requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 (env or settings.json
env). If a request clearly wants a team but the feature may be off, check
first and tell the user how to enable it rather than silently falling back to
doing everything solo:
// ~/.claude/settings.json
{
"env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" },
"teammateMode": "auto" // "auto" | "in-process" | "tmux"
}
teammateMode: auto (split panes if in tmux, else in-process), in-process
(cycle with Shift+Down), tmux (needs tmux/iTerm2; one pane per teammate).
Per-session override: claude --teammate-mode in-process. Teammate model is
set via /config → "Default teammate model" (does not inherit /model).
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.
- 2mo ago First seen · 135 lines · 161 tokens per session scan A 7b46acb8ca37
agent-teams is a skill published in the GitHub repository robconery/kolea (11 stars, last pushed 28d ago), licensed MIT. It adds 161 tokens to every session and 1,520 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
supermemory
Supermemory is a state-of-the-art memory and context infrastructure for AI agents. Use this skill when building applications that need persistent memory, user personalization, long-term context retention, or semantic search across knowledge bases. It provides Memory API for learned user context, User Profiles for…
email-drip-sequence
Write an email drip sequence for affiliate marketing. Triggers on: "write me an email sequence", "create a drip campaign", "email nurture sequence", "affiliate email funnel", "welcome email series", "email onboarding sequence", "write emails for my list", "set up a drip sequence", "email campaign for [product]"…
moemail
Use when an AI agent needs a temporary/disposable email address — for receiving verification emails, testing email integrations, or any task requiring a temporary inbox via the moemail CLI.
ui-and-theme
Frontend/design system skill for the svelteflare monorepo. Use this whenever the user wants to build or modify UI — pages, sections, components, layouts, forms, cards, tables, dialogs, dashboards, or landing pages. Also invoke for anything theme-related: light/dark mode, custom colors, design tokens, typography, or…
auth-db-billing
Backend product systems skill for the svelteflare monorepo. Invoke whenever the user wants to work with auth, sessions, protected routes, users, the database, schema changes, migrations, Stripe billing, subscriptions, paid feature gates, or any server-only logic in the Hono API. Trigger on "add a protected route"…
build-feature
Main orchestration skill for adding features to the svelteflare monorepo. Invoke whenever the user wants to add, build, implement, or create any new functionality — a page, API endpoint, DB table, form, component, auth-gated route, billing feature, or any combination. Trigger on "add X", "build X", "implement X", "I…