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 agents/untra/operator/codexgit clone --depth 1 https://github.com/untra/operatorWhat 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.00011 | $0.00343 |
| Opus 5 | $0.00005 | $0.00171 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
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 yesterday.
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
Codex is the OpenAI code-specialized CLI agent, available through the OpenAI API.
Status
Codex integration is currently experimental. Features may be limited compared to other agents.
Installation
Install the OpenAI CLI:
npm i -g @openai/codex
Plans and Pricing
View OpenAI Codex pricing page
Configuration
See the full Codex agent configuration reference.
Add Codex to your Operator configuration:
# ~/.config/operator/config.toml
[agents.codex]
enabled = true
api_key_env = "OPENAI_API_KEY"
model = "gpt-4"
Authentication
Set your OpenAI API key:
export OPENAI_API_KEY="your-api-key"
Or add it to your shell profile for persistence.
Multi-agent relay
Operator injects relay env vars (RELAY_HUB_SOCKET, RELAY_AGENT_NAME) into Codex sessions at launch so agents can discover each other by ticket ID. Full MCP tool support for Codex relay is planned for a future release.
See Relay for details.
API Usage
Codex uses the OpenAI API which has usage-based pricing. Monitor your usage at platform.openai.com.
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.
- yesterday First seen · 59 lines · 11 tokens per session scan A 7c3b6ccdc637
codex is an agent published in the GitHub repository untra/operator (36 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 343 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-30.
Other agents, from other repositories
code-reviewer
Review PRs against this checklist. Be concise - only comment on actual issues.
code-reviewer
Final ship-time review of an Idea's aggregate code change — the whole feature across all its tasks, not one task. Read-only; posts a VERDICT comment on the Idea. Spawn after the last task of an idea-rooted proposal is verified.
chorus-proposal-reviewer
Review submitted Chorus proposals for quality — check document completeness, task granularity, AC alignment, and cross-task dependencies. Spawn via the blocking subagent tool after choruspmsubmitproposal.
chorus-task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn via the blocking subagent tool after chorussubmitforverify.
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
chorus
You are the Chorus main agent for Amazon Kiro CLI. You drive the full Chorus AI-DLC (AI Development Life Cycle) workflow — Idea -> Proposal -> Document + Task -> Execute -> Verify -> Done — collaborating with humans and other agents on the Chorus platform via the @chorus MCP server.