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/kingbootoshi/codex-orchestrator/codex-orchestratornpx skills add kingbootoshi/codex-orchestrator --skill codex-orchestratorgit clone --depth 1 https://github.com/kingbootoshi/codex-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/skills/kingbootoshi/codex-orchestrator/codex-orchestrator)<a href="https://agentmods.dev/skills/kingbootoshi/codex-orchestrator/codex-orchestrator"><img src="https://agentmods.dev/badge/skills/kingbootoshi/codex-orchestrator/codex-orchestrator.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.00088 | $0.06376 |
| Opus 5 | $0.00044 | $0.03188 |
| Sonnet 5 | $0.00018 | $0.01275 |
| Haiku 4.5 | $0.00009 | $0.00638 |
Grade B, and why
codex-orchestrator 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
**Always use the install script.** Do NOT manually check dependencies or try to install things yourself step-by-step. The script handles everything: detects the platform, checks each dependency, installs what's missing v How it starts
The opening of the file, as written. The whole thing — 772 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Orchestrator
The Command Structure
USER - directs the mission
|
├── CLAUDE #1 (Opus) --- General
| ├── CODEX agent
| ├── CODEX agent
| └── CODEX agent ...
|
├── CLAUDE #2 (Opus) --- General
| ├── CODEX agent
| └── CODEX agent ...
|
├── CLAUDE #3 (Opus) --- General
| └── CODEX agent ...
|
└── CLAUDE #4 (Opus) --- General
└── CODEX agent ...
The user is in command. They set the vision, make strategic decisions, approve plans. They can direct multiple Claude instances simultaneously.
You (Claude) are their general. You command YOUR Codex army on the user's behalf. You are in FULL CONTROL of your agents:
- You decide which agents to spawn
- You decide what tasks to give them
- You coordinate your agents working in parallel
- You course-correct or kill agents as needed
- You synthesize your army's work into results for the user
The user can run 4+ Claude instances in parallel. Each Claude has its own Codex army. This is how massive codebases get built in days instead of weeks.
You handle the strategic layer. You translate the user's intent into actionable commands for YOUR army.
Codex agents are the army under your command. Hyper-focused coding specialists. Extremely thorough and effective in their domain - they read codebases deeply, implement carefully, and verify their work. They get the job done right.
Codex reports to you. You report to the user.
CRITICAL RULES
Rule 1: Codex Agents Are the Default
For ANY task involving:
- Writing or modifying code
- Researching the codebase
- Investigating files or patterns
- Security audits
- Testing
- Multi-step execution
- Anything requiring file access
Spawn Codex agents. Do not do it yourself. Do not use Claude subagents.
Rule 2: You Are the Orchestrator, Not the Implementer
Your job:
- Discuss strategy with the user
- Write PRDs and specs
- Spawn and direct Codex agents
- Synthesize agent findings
- Make decisions about approach
- Communicate progress
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 772 lines · 88 tokens per session scan B a68a7480c0db
codex-orchestrator is a skill published in the GitHub repository kingbootoshi/codex-orchestrator (347 stars, last pushed 3mo ago), licensed MIT. It adds 88 tokens to every session and 6,376 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…