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/sean-sunagaku/claude-code-plugin/agent-teamnpx skills add sean-sunagaku/claude-code-plugin --skill agent-teamgit clone --depth 1 https://github.com/sean-sunagaku/claude-code-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/sean-sunagaku/claude-code-plugin/agent-team)<a href="https://agentmods.dev/skills/sean-sunagaku/claude-code-plugin/agent-team"><img src="https://agentmods.dev/badge/skills/sean-sunagaku/claude-code-plugin/agent-team.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.1 | $0.00065 | $0.01659 |
| Opus 5 | $0.00032 | $0.00830 |
| Sonnet 5 | $0.00013 | $0.00332 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
agent-team 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 5d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Team Orchestration
Orchestrate multi-agent teams to decompose complex tasks, select optimal sub-agents, and execute work in parallel.
When to Use
- Tasks requiring parallel work across multiple domains (frontend + backend, research + implementation)
- Complex multi-step tasks benefiting from specialization (plan, implement, test, review)
- Large-scale refactoring or feature development spanning many files
- Tasks requiring both research and implementation phases
Core Workflow
1. Task Decomposition
Analyze the user's request and break it into independent, parallelizable units:
- Identify the goal and deliverables
- Split into sub-tasks that can run concurrently
- Identify dependencies between sub-tasks (what blocks what)
- Assign each sub-task to the optimal agent type
2. Agent Type Selection
Select the optimal subagent_type for each sub-task based on the work required.
Built-in Agents
| Agent Type | Best For | Tools Available |
|---|---|---|
general-purpose |
Implementation, file editing, full-stack work | All tools (Read, Write, Edit, Bash, Glob, Grep, etc.) |
Explore |
Codebase research, finding patterns, understanding architecture | Read-only (Glob, Grep, Read, WebFetch, WebSearch) |
Plan |
Design decisions, architecture planning, implementation strategy | Read-only (same as Explore) |
Bash |
Git operations, build commands, CLI tasks | Bash only |
code-simplifier |
Refactoring, cleanup, code quality improvements | All tools |
Project Custom Agents (.claude/agents/)
Specialized agents with project-specific context pre-loaded. Prefer these over general-purpose when the task falls within their domain.
| Agent Type | Domain | Scope Restriction |
|---|---|---|
backend-dev |
Hono + Drizzle ORM + SQLite API 実装 | packages/server/ のみ |
frontend-dev |
Next.js 16 + React 19 + Tailwind UI 実装 | packages/web/ のみ |
tester |
Vitest テスト設計・実装・実行 | packages/server/src/__tests__/ |
Custom agents already know the project's coding conventions, file structure, and reference files -- no need to repeat this context in the prompt.
What ships with it
5 files 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.
- 5d ago First seen · 196 lines · 65 tokens per session scan A 081c66dbabb6
agent-team is a skill published in the GitHub repository sean-sunagaku/claude-code-plugin (36 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,659 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-08-30.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…