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 epicsagas/plugins --skill teamsgit clone --depth 1 https://github.com/epicsagas/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/epicsagas/plugins/teams)<a href="https://agentmods.dev/skills/epicsagas/plugins/teams"><img src="https://agentmods.dev/badge/skills/epicsagas/plugins/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/epicsagas/plugins/teams"><img src="https://agentmods.dev/badge/skills/epicsagas/plugins/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.00051 | $0.00464 |
| Opus 5 | $0.00026 | $0.00232 |
| Sonnet 5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
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.
What it actually says
Manage agent teams for multi-agent coordination. List, sync, and compose teams of specialized agents.
Usage
/teams list — show all teams
/teams show <name> — show team details
/teams sync <name> — sync team agents to current project
/teams design — interactive team composition
Quick reference
List teams
# Via tool
harness_team_list
# Or CLI
epic team list
Show team details
# Via tool
harness_team_show(team="core")
# Or CLI
epic team show core
Sync team to project
# Via tool — sync to .claude/agents/ in current project
harness_team_sync(team="core")
# Via tool — sync globally to ~/.claude/agents/
harness_team_sync(team="core", global=true)
Team composition guidelines
A well-designed team covers these roles:
| Role | Purpose | Example agents |
|---|---|---|
| Leader | Coordinates, assigns tasks, reviews | architect, project-lead |
| Researcher | Explores code, finds information | explorer, researcher |
| Builder | Writes implementation code | coder, implementer |
| Reviewer | Quality gate, testing | reviewer, tester |
Workflow: setting up a team
harness_team_list— see what's availableharness_team_show(team="<name>")— inspect the teamharness_team_sync(team="<name>")— sync agents to project- Agents appear in
.claude/agents/and are ready to use
Designing a new team
For custom teams, run epic team (no subcommand) for interactive design.
The CLI walks through role selection, skill assignment, and agent configuration.
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 · 71 lines · 51 tokens per session scan A 10f7eb8b4cbf
teams is a skill published in the GitHub repository epicsagas/plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 464 once invoked, about $0.0003 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-05.
Other skills, from other repositories
deps-audit
Use when auditing, updating, or securing project dependencies. Covers multi-language dependency detection, security vulnerability scanning, outdated package identification, unused dependency detection, and update strategies for npm, pip, cargo, and go.
git-advanced
Use when performing complex git operations -- rebasing, cherry-picking, resolving merge conflicts, bisecting bugs, managing stashes, cleaning history, or working with monorepos. Goes beyond basic commit/push/pull.
refactoring
Use when restructuring code without changing behavior -- extracting functions, renaming, moving files, reducing duplication, migrating between patterns (JS to TS, CJS to ESM), or addressing code smells. Covers safe refactoring workflows for any language.
repo-polish
Use when setting up new repositories, auditing existing ones, or preparing repos for public visibility. Generates .gitignore, .env.example, README, and LICENSE files. Detects committed secrets and flags security issues.
starter-session-audit
Use when the user asks to audit a session for uncaptured learnings. Activates on "audit this session", "session audit", "what did we miss", "end of session check", or "/starter-session-audit". Scans the conversation for corrections, preferences, decisions, and new context, then proposes where to save each.
clean-code
Use when the user writes new Python, or asks for review, refactor, or cleanup of Python code, names, comments/docstrings, functions, or tests. Applies Robert Martin's complete Clean Code catalog -- naming, functions, comments, DRY, boundary conditions, and tests -- to the code being changed.