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 skills add patrick-fu/awesome-skills --skill codex-coding-agentgit clone --depth 1 https://github.com/patrick-fu/awesome-skillsWrote 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/patrick-fu/awesome-skills/codex-coding-agent)<a href="https://agentmods.dev/skills/patrick-fu/awesome-skills/codex-coding-agent"><img src="https://agentmods.dev/badge/skills/patrick-fu/awesome-skills/codex-coding-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/patrick-fu/awesome-skills/codex-coding-agent"><img src="https://agentmods.dev/badge/skills/patrick-fu/awesome-skills/codex-coding-agent.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.00490 |
| Opus 5.5 | $0.00008 | $0.00196 |
| Sonnet 5.5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
codex-coding-agent 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 3d 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.
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.
This is a copy
89% identical to claude-code-coding-agent — 54 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Coding Agent
Scope
Use the selected launcher's --version, --help, exec --help and model
catalog (debug models; extract only model/effort fields)
to choose supported model/effort settings. Honor explicit choices; keep wrappers
opaque because their source and environment may contain credentials. Compare
requested settings with observed evidence, leaving absent values unverified.
Fix the workspace, permitted actions and acceptance evidence. Experiments and parallel writers need isolated workspaces. Boundary: before file-only work, strict confinement or permission recovery, read Boundaries. The skill grants no extra scope.
Run
For ordinary bounded headless tasks, use codex_run.py:
python3 "$SKILL_DIR/scripts/codex_run.py" run \
--launcher "$LAUNCHER" --cwd "$WORKSPACE" --prompt-file "$PROMPT_FILE" \
--timeout-seconds 600 -- --model "$MODEL"
SKILL_DIR is this skill's directory. Choose the deadline deliberately
(0 is unbounded); pass authorized Codex exec options after --.
Omit model overrides supplied by an opaque wrapper.
| Owner | Responsibility |
|---|---|
| Script | Target/prompt validation, native transport, unique captures, real child exit, compact receipt |
| Agent | Model, permissions, required successful actions, artifacts, recovery |
Retain the host process handle. The runner prints run_dir, then its receipt;
use python3 "$SKILL_DIR/scripts/codex_run.py" inspect "$RUN_DIR" while
waiting. Quiet output alone is not failure.
Accept
COMPLETED means process/stream completion, not task acceptance. Read
answer.txt; check necessary successful tools, refusals and artifacts/diff,
including untracked files. Missing or empty candidate text may be legitimate;
judge against Scope. Report unperformed checks.
Decode: for schema questions, read Stream.
Recover: before cancellation recovery, another attempt or native resume,
read Recovery.
What ships with it
8 files 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.
- 3d ago Changed · -25 lines · -8 tokens per session abb13aadd15a
- 15d ago Changed · -24 lines de8c0dd9b80a
- 27d ago Changed · +14 lines 1d8f4bab87c4
- 1mo ago First seen · 88 lines · 29 tokens per session scan A 00b50aaaa2e9
codex-coding-agent is a skill published in the GitHub repository patrick-fu/awesome-skills (69 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 490 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to claude-code-coding-agent, differing in 54 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…