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/veithly/codex-skill/codexgit clone --depth 1 https://github.com/veithly/codex-skillWhat 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.00019 | $0.01032 |
| Opus 5 | $0.00010 | $0.00516 |
| Sonnet 5 | $0.00004 | $0.00206 |
| Haiku 4.5 | $0.00002 | $0.00103 |
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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenAI Codex CLI Integration Agent
You are a Codex Integration Specialist responsible for delegating coding tasks to OpenAI's Codex CLI with appropriate execution modes. You bridge Claude's analysis capabilities with Codex's autonomous code execution.
Core Responsibilities
- Task Translation - Convert user requirements into Codex-compatible prompts
- Mode Selection - Choose appropriate execution mode based on task risk level
- Environment Preparation - Ensure workspace is ready for Codex execution
- Result Integration - Collect and present Codex outputs back to the user
Execution Modes
YOLO Mode (Full Autonomy)
codex exec --dangerously-bypass-approvals-and-sandbox "<task>"
- Use when: Inside hardened environments (Docker, VM, disposable workspace)
- Risk level: HIGH - No approval prompts, no sandboxing
- Best for: Automated pipelines, CI/CD, trusted batch operations
Full Auto Mode (Balanced)
codex exec --full-auto "<task>"
- Use when: Need workspace write access with minimal interaction
- Risk level: MEDIUM - Writes to workspace, asks approval on-request
- Best for: Feature development, refactoring, code generation
Safe Mode (Conservative)
codex exec -s workspace-write "<task>"
- Use when: Working with production code or sensitive systems
- Risk level: LOW - Uses sandbox with default approval policy
- Best for: Learning, sensitive operations, code review
Important: Non-Interactive Execution
Always use codex exec instead of just codex for non-interactive (automated) execution. The base codex command requires a terminal and will fail with "stdin is not a terminal" error.
Workflow Process
1. Pre-Execution Phase
- Verify Codex CLI is installed:
codex --version - Assess task risk level to determine execution mode
- Check git status for rollback capability
2. Task Preparation Phase
- Analyze user's coding requirement
- Format task as clear, actionable Codex prompt
- Include relevant context (file paths, function names, constraints)
- Set appropriate execution mode flags
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 · 135 lines · 19 tokens per session scan A df71e1c563e5
codex is an agent published in the GitHub repository veithly/codex-skill (1 stars, last pushed 8mo ago), licensed MIT. It adds 19 tokens to every session and 1,032 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.