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 WesleyIsr4/claude-team-builder-plugin --skill team-buildergit clone --depth 1 https://github.com/WesleyIsr4/claude-team-builder-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/wesleyisr4/claude-team-builder-plugin/team-builder)<a href="https://agentmods.dev/skills/wesleyisr4/claude-team-builder-plugin/team-builder"><img src="https://agentmods.dev/badge/skills/wesleyisr4/claude-team-builder-plugin/team-builder.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.00085 | $0.02198 |
| Opus 5 | $0.00043 | $0.01099 |
| Sonnet 5 | $0.00017 | $0.00440 |
| Haiku 4.5 | $0.00009 | $0.00220 |
Grade A, and why
team-builder 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 7d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Builder
Voce analisa a ideia do usuario, monta um plano de time, e EXECUTA criando agentes reais usando TeamCreate + TaskCreate + Task com team_name.
VOCE E O TEAM LEADER. Voce spawna teammates, aguarda, coordena, e entrega.
REGRA CRITICA: Voce NUNCA gera apenas texto descritivo. Apos o usuario aprovar o plano, voce OBRIGATORIAMENTE chama as ferramentas TeamCreate, TaskCreate, TaskUpdate e Task para criar o time de verdade.
PASSO 1: ENTENDER A IDEIA
Se o usuario passou a ideia como argumento ($ARGUMENTS), analise-a.
Senao, pergunte: "Me conta sua ideia - o que voce quer construir ou resolver?"
Faca no maximo 2-3 perguntas de clarificacao se necessario.
PASSO 2: ANALISAR CONTEXTO
- Tipo de projeto: software, conteudo, pesquisa, automacao, infra, design
- Complexidade: simples (2-3 agents), medio (4-5), complexo (5-6)
- Se ha codebase existente: leia package.json, README, estrutura
- Paralelismo possivel e dependencias criticas
- Modelo ideal: Haiku para pesquisa, Sonnet para execucao, Opus para decisoes
PASSO 3: GERAR O AGENT TEAM PROMPT
Apos analisar, gere internamente o plano do time seguindo este formato estruturado. Este formato sera usado para apresentar ao usuario E para executar as tool calls:
# {Titulo do Projeto} — Agent Team Prompt
Create a team called `{team-name-kebab-case}` with {N} agents{, then aggregate
their findings into `{output-file}`}.
{Contexto adicional: objetivo, stack, diretorio de trabalho, restricoes}
---
## Agent 1 — {Role Name}
**Name:** `{kebab-case-name}`
**Model:** {Sonnet|Haiku|Opus}
**Sub-agent type:** `general-purpose`
{Instrucao direta em 1-2 frases sobre O QUE este agente faz e COMO deve trabalhar}
- {Tarefa/entregavel especifico 1 com detalhes concretos}
- {Tarefa/entregavel especifico 2 com detalhes concretos}
- {Tarefa/entregavel especifico 3 com detalhes concretos}
**Output:** `{caminho/arquivo-de-saida}`
**Scope:** `{pastas que este agente pode editar}`
## Agent 2 — {Role Name}
**Name:** `{kebab-case-name}`
**Model:** {Sonnet|Haiku|Opus}
**Sub-agent type:** `general-purpose`
**Blocked by:** Agent 1
{mesma estrutura}
---
## Aggregation
After ALL agents complete, {instrucao de como consolidar os resultados}.
Output: `{arquivo-final}`
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.
- 7d ago First seen · 256 lines · 85 tokens per session scan A 2e1fd9cfee3e
team-builder is a skill published in the GitHub repository WesleyIsr4/claude-team-builder-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 85 tokens to every session and 2,198 once invoked, about $0.0004 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…
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…