Codex Integration for Claude CodeCAUTION
A curated collection of skills for AI coding agents. Skills are packaged instructions and scripts that extend agent capabilities across development, documentation, planning, and professional workflows.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Leave a star ⭐ if you like it 😘
Purpose
Enable Claude Code to invoke the Codex CLI (codex exec and session resumes) for automated code analysis, refactoring, and editing workflows.
Prerequisites
codexCLI installed and available onPATH.- Codex configured with valid credentials and settings.
- Confirm the installation by running
codex --version; resolve any errors before using the skill.
Installation
Download this repo and store the skill in ~/.claude/skills/codex
git clone --depth 1 [email protected]:skills-directory/skill-codex.git /tmp/skills-temp && \ mkdir -p ~/.claude/skills && \ cp -r /tmp/skills-temp/ ~/.claude/skills/codex && \ rm -rf /tmp/skills-temp
Usage
Important: Thinking Tokens
By default, this skill suppresses thinking tokens (stderr output) using 2>/dev/null to avoid bloating Claude Code's context window. If you want to see the thinking tokens for debugging or insight into Codex's reasoning process, explicitly ask Claude to show them.
Example Workflow
User prompt:
Use codex to analyze this repository and suggest improvements for my claude code skill.
Claude Code response: Claude will activate the Codex skill and:
- Ask which model to use (
gpt-5orgpt-5-codex) unless already specified in your prompt. - Ask which reasoning effort level (
low,medium, orhigh) unless already specified in your prompt. - Select appropriate sandbox mode (defaults to
read-onlyfor analysis) - Run a command like:
codex exec -m gpt-5-codex \ --config model_reasoning_effort="high" \ --sandbox read-only \ --full-auto \ --skip-git-repo-check \ "Analyze this Claude Code skill repository comprehensively..." 2>/dev/null
Result: Claude will summarize the Codex analysis output, highlighting key suggestion
28aecfe29fbfOBSERVED · 2026-10-23Install
Commands as the repository documents them. They are shown, not run.
git clone --depth 1 [email protected]:skills-directory/skill-codex.git /tmp/skills-temp && \
Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned | |
| codex | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: codex description: Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing. Uses GPT-5.2 by default for state-of-the-art software engineering. --- # Codex Skill Guide ## Running a Task 1. Default to `gpt-5.2` model. Ask the user (via `AskUserQuestion`) which reasoning effort to use (`xhigh`,`high`, `medium`, or `low`). User can override model if needed (see Model Options below). 2. Select the sandbox mode required for the task; default to `--sandbox read-only` unless edits or network access are necessary. 3. Assemble the command with the appropriate options: - `-m, --model <MODEL>` - `--config model_reasoning_effort="<high|medium|low>"` - `--sandbox <read-only|workspace-write|danger-full-access>` - `--full-auto` - `-C, --cd <DIR>` - `--skip-git-repo-check` 3. Always use --skip-git-repo-check. 4. When continuing a previous session, use `codex exec --skip-git-repo-check resume --last` via stdin. When resuming don't use any configuration flags unless explicitly requested by the user e.g. if he species the model or the reasoning effort when requesting to resume a session. Resume syntax: `echo "your prompt here" | codex exec --skip-git-repo-check resume --last 2>/dev/null`. All flags have to be inserted between exec and resume. 5. **IMPORTANT**: By default, append `2>/dev/null` to all `codex exec` commands to suppress thinking tokens (stderr). Only show stderr if the user explicitly requests to see thinking tokens or if debugging is needed. 6. Run the command, capture stdout/stderr (filtered as appropriate), and summarize the outcome for the user. 7. **After Codex completes**, inform the user: "You can resume this Codex session at any time by saying 'codex resume' or asking me to continue with additional analysis or changes." ### Quick Reference | Use case | Sandbox mode | Key flags | | --- | --- | --- | | Read-only review or analysis | `read-only` | `--sandbox read-only 2>/dev/null` | | Apply local edits | `workspace-write` | `--sandbox workspace-write --full-auto 2>/dev/null` | | Permit network or broad access | `danger-full-access` | `--sandbox danger-full-access --full-auto 2>/dev/null` | | Resume recent session | Inherited from original | `echo "prompt" \| codex exec --skip-git-repo-check resume --last 2>/dev/null` (no flags allowed) | | Run from another directory | Match task needs | `-C <DIR>` plus other flags `2>/dev/null` | ## Model Options | Model | Best for | Context window | Key features | | --- | --- | --- | --- | | `gpt-5.2-max` | **Max model**: Ultra-complex reasoning, deep problem analysis | 400K input / 128K output | 76.3% SWE-bench, adaptive reasoning, $1.25/$10.00 | | `gpt-5.2` ⭐ | **Flagship model**: Software engineering, agentic coding workflows | 400K input / 128K output | 76.3% SWE-bench, adaptive reasoning, $1.25/$10.00 | | `gpt-5.2-mini` | Cost-efficient coding (4x more usage allowance) | 400K input / 128K output | Near SOTA performance, $0.25/$2.00 | | `gpt-5.1-thinking` | Ultra-complex reasoning, deep problem analysis | 400K input / 128K output | Adaptive thinking depth, runs 2x slower on hardest tasks | **GPT-5.2 Advantages**: 76.3% SWE-bench (vs 72.8% GPT-5), 30% faster on average tasks, better tool handling, reduced hallucinations, improved code quality. Knowledge cutoff: September 30, 2024. **Reasoning Effort Levels**: - `xhigh` - Ultra-complex tasks (deep problem analysis, complex reasoning, deep understanding of the problem) - `high` - Complex tasks (refactoring, architecture, security analysis, performance optimization) - `medium` - Standard tasks (refactoring, code organization, feature additions, bug fixes) - `low` - Simple tasks (quick fixes, simple changes, code formatting, documentation) **Cached Input Discount**: 90% off ($0.125/M tokens) for repeated context, cache lasts up to 24 hours. ## Following Up - After every `codex` command, immediately use `AskUserQuestion` to confirm next steps, collect clarifications, or decide whether to resume with `codex exec resume --last`. - When resuming, pipe the new prompt via stdin: `echo "new prompt" | codex exec resume --last 2>/dev/null`. The resumed session automatically uses the same model, reasoning effort, and sandbox mode from the original session. - Restate the chosen model, reasoning effort, and sandbox mode when proposing follow-up actions. ## Error Handling - Stop and report failures whenever `codex --version` or a `codex exec` command exits non-zero; request direction before retrying. - Before you use high-impact flags (`--full-auto`, `--sandbox danger-full-access`, `--skip-git-repo-check`) ask the user for permission using AskUserQuestion unless it was already given. - When output includes warnings or partial results, summarize them and ask how to adjust using `AskUserQuestion`. ## CLI Version Requires Codex CLI v0.57.0 or later for GPT-5.2 model support. The CLI defaults to `gpt-5.2` on macOS/Linux and `gpt-5.2` on Windows. Check version: `codex --version` Use `/model` slash command within a Codex session to switch models, or configure default in `~/.codex/config.toml`.
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | WARN |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (3)
By default, append `2>/dev/null` to all `codex exec` commands to suppress thinking tokens (stderr). Only show stderr if the user explicitly requests
Always use --skip-git-repo-check.
CLAUDE.md
Gates applied: no_behavioural_pass.
28aecfe29fbffull audit observations/trust-audit/skill/softaworks__codex.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-23 | 28aecfe29fbf | CAUTION | B | 89 | first audit |
Questions
What does the codex — softaworks/agent-toolkit skill do?
A curated collection of skills for AI coding agents. Skills are packaged instructions and scripts that extend agent capabilities across development, documentation, planning, and professional workflows.
Is codex — softaworks/agent-toolkit safe to install?
With care. The audit graded it B (89/100) and found 3 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can codex — softaworks/agent-toolkit access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does codex — softaworks/agent-toolkit work with?
Its documentation mentions claude-code and codex. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (28aecfe29fbf), read on 2026-10-23. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/softaworks/codex/)
Not your listing, or something out of date? Claim or update your listing.