Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add kellvembarbosa/team-orchestrator/plugin install teamWrote 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/commands/kellvembarbosa/team-orchestrator/setup-claude)<a href="https://agentmods.dev/commands/kellvembarbosa/team-orchestrator/setup-claude"><img src="https://agentmods.dev/badge/commands/kellvembarbosa/team-orchestrator/setup-claude.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.00020 | $0.00083 |
| Opus 5 | $0.00010 | $0.00042 |
| Sonnet 5 | $0.00004 | $0.00017 |
| Haiku 4.5 | $0.00002 | $0.00008 |
Grade B, and why
setup-claude scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
description: Enable CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in ~/.claude/settings.json What it actually says
!bash "${CLAUDE_PLUGIN_ROOT}/bin/team" setup-claude
Remind the user that Claude Code v2.1.32+ is required for agent teams, and that they must restart Claude Code for the env var change to take effect.
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 · 9 lines · 20 tokens per session scan B 455f8b43391d
setup-claude is a command published in the GitHub repository kellvembarbosa/team-orchestrator (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 83 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
octo-auto
Smart router - Single entry point with natural language intent detection.
octo-design-ui-ux
Design UI/UX systems with style guides, palettes, typography, and component specs.
octo-pipeline
Run content analysis pipeline on URL(s) to extract patterns and create anatomy guides.
verify
Fidelity check — rebuild a page from the extracted tokens, pixel-diff it against the live site, and score how faithfully the tokens capture the design.
battle
Head-to-head graded battle card between two sites — eight dimensions, bar-by-bar, verdict line.
octo
This v10 compatibility command delegates to /octo:auto. It is scheduled for removal in v11.