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/leejuoh/claude-code-zero/codex-setupnpx skills add LeeJuOh/claude-code-zero --skill codex-setupgit clone --depth 1 https://github.com/LeeJuOh/claude-code-zeroWhat 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.00050 | $0.01392 |
| Opus 5 | $0.00025 | $0.00696 |
| Sonnet 5 | $0.00010 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade B, and why
codex-setup 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.codex/config.toml 2>/dev/null || echo "NO_CONFIG" How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Setup & Configuration
Preflight check and ~/.codex/config.toml configuration helper for codex-advisor.
Mode Selection
Parse $ARGUMENTS:
| Input | Action |
|---|---|
--status or no args |
Run preflight + show current config |
--model MODEL |
Set default model in config.toml |
--effort LEVEL |
Set reasoning effort in config.toml |
| Combined flags | Apply all settings |
Preflight Check
Check Codex CLI
which codex >/dev/null 2>&1 && codex --version || echo "NOT_INSTALLED"
If NOT_INSTALLED: "Codex CLI is not installed. Install: npm install -g @openai/codex"
Check Authentication
codex --version 2>&1
If output contains "not authenticated" or "OPENAI_API_KEY": "Authentication required. Run: codex login"
If version prints normally: auth is likely OK (full verification happens on first real command).
Check Official Codex Plugin
CODEX_COMPANION=$("${CLAUDE_PLUGIN_ROOT}/scripts/resolve-companion.sh")
If exit code non-zero (plugin not found), guide the user through the full installation process:
- Tell the user to run these commands in order (they must type these themselves since they are interactive CLI commands):
/plugin marketplace add openai/codex-plugin-cc— adds the Official Codex marketplace/plugin install codex@openai-codex— installs the plugin from that marketplace/reload-plugins— activates the newly installed plugin
- After the user completes the steps, re-run the companion check to verify.
Do NOT just print the steps and move on. Wait for the user to complete them.
If found, run setup check:
node "$CODEX_COMPANION" setup --json
Include the setup output in the status report.
Configuration Management
Read current config
cat ~/.codex/config.toml 2>/dev/null || echo "NO_CONFIG"
Set Model / Effort (--model, --effort)
Both flags are handled by one call. Empty string = no change for that field:
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.
- 2d ago First seen · 128 lines · 50 tokens per session scan B ef6c98f1bb51
codex-setup is a skill published in the GitHub repository LeeJuOh/claude-code-zero (51 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 1,392 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…