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/toffyui/ccteams/use-teamnpx skills add toffyui/ccteams --skill use-teamgit clone --depth 1 https://github.com/toffyui/ccteamsWrote 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/toffyui/ccteams/use-team)<a href="https://agentmods.dev/skills/toffyui/ccteams/use-team"><img src="https://agentmods.dev/badge/skills/toffyui/ccteams/use-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.00025 | $0.00489 |
| Opus 5 | $0.00013 | $0.00244 |
| Sonnet 5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
use-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 6d 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
Apply the agent team specified by the user's argument to the current project.
Steps:
-
If no team name was provided, run
ccteams listvia Bash, show the output, and ask the user which team they want to apply before proceeding. -
Decide whether to pass
--agent-teams:- Pass
--agent-teamsif the user's request uses any of these phrases or clear synonyms: "agent-teams mode", "collaborative", "team mode", "teammates working in parallel", "have them work together", "parallel teammates", "member messaging". - Otherwise, run the plain form.
- Pass
-
Decide whether to pass
--profile <p>(model profile — remaps each agent's model at apply time):--profile budgetif the user asks for the cheap / economical / token-saving setup ("cheapest", "save tokens", "budget", "haiku builders").--profile maxif the user asks for maximum quality regardless of cost ("best quality", "all opus", "strongest models").- Otherwise omit the flag —
balanced(the shipped sonnet/opus defaults) is the default. Never add a profile the user did not ask for.
-
Run the command via Bash, combining the flags decided above:
ccteams use <team-name> [--agent-teams] [--profile <p>]--agent-teamsenables Claude Code's experimental agent-teams feature (CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in .claude/settings.json), which allows teammates to message each other. It is opt-in; you never add it unless the user asked. -
Relay ccteams's full output to the user — do not truncate or paraphrase it.
-
Explicitly repeat the session-restart instruction from ccteams's output: agents load at session start only; the switch is NOT instantly active. The user must run
/exitthenclaudeto activate the new team.
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.
- 6d ago First seen · 41 lines · 25 tokens per session scan A 3075f053d0f3
use-team is a skill published in the GitHub repository toffyui/ccteams (47 stars, last pushed 6d ago), licensed MIT. It adds 25 tokens to every session and 489 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-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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…