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 travisjneuman/.claude --skill agent-teamsgit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/agent-teams)<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.
<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>- 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.00024 | $0.00597 |
| Opus 5 | $0.00012 | $0.00298 |
| Sonnet 5 | $0.00005 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
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 9d 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 — 81 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.
When to Suggest Agent Teams
Proactively suggest agent teams 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 + Test coverage reviewer. Each reviews independently, then lead synthesizes findings.
Feature Dev (3 teammates)
Architect (plan approval required) + Implementer + Test writer. Architect plans first, implementer follows, test writer validates.
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.
Spawn Prompt Formula
Every spawn prompt should include:
- Role: "You are the [role] teammate responsible for [domain]"
- Files: "You own files in [directories]. Do not modify files outside your scope."
- Focus: "Specifically look for / implement [details]"
- Context: "[Project-specific information the teammate needs]"
- Deliverable: "Report your findings as [format] / Implement [specific output]"
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.
- 9d ago First seen · 81 lines · 24 tokens per session scan A 8e38c53a7f71
agent-teams is a skill published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 597 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-09-03.
Other skills, from other repositories
incremental-shipping
Use when implementing a non-trivial feature, migration, or refactor that would otherwise be a single large change. Activate for keywords like "feature flag", "incremental", "vertical slice", "migration", "rollout", "behind a flag", "ship small". Enforces vertical slicing, feature-flagged rollout, and refactor-with…
to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
bootstrap-monorepo
Autonomous polyglot monorepo bootstrap meta-prompt on the moon + proto + Bun stack (Nx-convergent). TRIGGERS - new monorepo, new repository, polyglot setup, scaffold repo, moon proto bootstrap, monorepo from scratch.
plan-review-experience
Experience-dimension reviewer for written plans (UX + DX). Use when running plan-review or directly when an experience review is wanted. Activate for keywords like "UX review", "DX review", "experience review", "error states", "API ergonomics", "developer experience", "user states". Scores 5 sub-dimensions 0-10…
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…