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 commands/kellvembarbosa/team-orchestrator/setup-codexgit clone --depth 1 https://github.com/kellvembarbosa/team-orchestratorWrote 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-codex)<a href="https://agentmods.dev/commands/kellvembarbosa/team-orchestrator/setup-codex"><img src="https://agentmods.dev/badge/commands/kellvembarbosa/team-orchestrator/setup-codex.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 | $0.00016 | $0.00105 |
| Opus 5 | $0.00008 | $0.00053 |
| Sonnet 5 | $0.00003 | $0.00021 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
setup-codex 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 3d 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
!bash "${CLAUDE_PLUGIN_ROOT}/bin/team" setup-codex
After this runs, every /team:new will also write a ~/.codex/agents/<name>.toml so Codex can spawn the same teams as subagents. Codex doesn't use slash commands — invoke a team there with natural language: "spawn the subagent".
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.
- 3d ago First seen · 9 lines · 16 tokens per session scan A 909d5fd60954
setup-codex is a command published in the GitHub repository kellvembarbosa/team-orchestrator (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 105 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-31.
Other commands, from other repositories
spec-research
需求 → 约束集（并行探索 + OPSX 提案）.
update-workflow
Regenerate an existing custom workflow's shortcut command wiring from the current swarm template.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
Team: Dev Loop
Spawn an implementer + verifier (+ optional planner) team that iterates on a scoped change until a deterministic check passes. Lead stays light.
weekly-review
Works for you. Go outside and live. — AI orchestrator that auto-routes tasks to the cheapest model that solves them. 70% run free on local models. Self-auditing, self-improving, zero prompting skill needed. Built with vibe coding by a finance student. Your models, your data.
plan
Start a structured interview to create a Product Requirements Document (PRD) that can be executed by KARIMO agents.