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 romiluz13/cc-teams --skill cc-teams-leadgit clone --depth 1 https://github.com/romiluz13/cc-teamsWrote 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/romiluz13/cc-teams/cc-teams-lead)<a href="https://agentmods.dev/skills/romiluz13/cc-teams/cc-teams-lead"><img src="https://agentmods.dev/badge/skills/romiluz13/cc-teams/cc-teams-lead/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/romiluz13/cc-teams/cc-teams-lead"><img src="https://agentmods.dev/badge/skills/romiluz13/cc-teams/cc-teams-lead.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.00217 | $0.28140 |
| Opus 5 | $0.00109 | $0.14070 |
| Sonnet 5 | $0.00043 | $0.05628 |
| Haiku 4.5 | $0.00022 | $0.02814 |
Grade A, and why
cc-teams-lead 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 — 2,216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CC-Teams Lead
EXECUTION ENGINE. When loaded: Detect intent → Load memory → Create Agent Team → Execute workflow → Collect contracts → Update memory → Shutdown team.
NEVER list capabilities. ALWAYS execute.
MODE: DELEGATE. The lead NEVER implements code. The lead creates teams, assigns tasks, collects results, and persists memory. Press Shift+Tab to enter delegate mode after team creation.
Decision Tree (FOLLOW IN ORDER)
| Priority | Signal | Keywords | Workflow |
|---|---|---|---|
| 1 | ERROR | error, bug, fix, broken, crash, fail, debug, troubleshoot, issue, problem, doesn't work | DEBUG (Bug Court) |
| 2 | PLAN | plan, design, architect, roadmap, strategy, spec, "before we build", "how should we" | PLAN (Single Planner) |
| 3 | REVIEW | review, audit, check, analyze, assess, "what do you think", "is this good" | REVIEW (Review Arena) |
| 4 | DEFAULT | Everything else | BUILD (Pair Build) |
Conflict Resolution: ERROR signals always win. "fix the build" = DEBUG (not BUILD).
Agent Teams / Protocol Summary
| Workflow | Protocol | Team Composition |
|---|---|---|
| REVIEW | cc-teams:review-arena |
3–5 reviewers (security, performance, quality + conditional a11y/api-contract) |
| DEBUG | cc-teams:bug-court |
2-5 investigators → builder fix → Review Arena (3–5 reviewers + challenge) → verifier |
| BUILD | cc-teams:pair-build |
Builder + Live Reviewer → Hunter → Review Arena (3–5 reviewers + challenge) → Verifier |
| PLAN | cc-teams:planning-patterns |
Single planner (NO plan mode — planner writes docs directly, lead reviews after) |
Agent Teams Preflight (MANDATORY)
Before creating or resuming any workflow:
-
Agent Teams enabled
- Confirm
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1in environment/settings. - If not enabled: stop and ask user to enable (do not run fallback orchestration).
- Confirm
-
Single active team policy
- One lead can manage one team at a time.
- If an old team is still active in this session: shut it down and
TeamDelete()before starting a new workflow.
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 · 2,216 lines · 217 tokens per session scan A c051fc459e2b
cc-teams-lead is a skill published in the GitHub repository romiluz13/cc-teams (5 stars, last pushed 5mo ago), licensed MIT. It adds 217 tokens to every session and 28,140 once invoked, about $0.0011 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-31.
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…
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…
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…