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/thesylvester/agentic-coding-tools/codex-agentnpx skills add TheSylvester/agentic-coding-tools --skill codex-agentgit clone --depth 1 https://github.com/TheSylvester/agentic-coding-toolsWhat 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.00084 | $0.01607 |
| Opus 5 | $0.00042 | $0.00804 |
| Sonnet 5 | $0.00017 | $0.00321 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
codex-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 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.
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Agent (wrapper)
This runs an autonomous agent with approvals and sandboxing disabled. The wrapper invokes
codex exec --dangerously-bypass-approvals-and-sandbox, because a non-interactive run has no one to approve anything. The child agent can read, write and execute in whatever directory you launch it from. Only give it briefs you would be willing to run yourself.
Execution
Works in both foreground and background:
# Foreground (blocks until done - use a long timeout, runs can take minutes)
Bash(command: "node \"~/.claude/skills/codex-agent/scripts/codex-agent.mjs\" Your prompt here", timeout: 600000)
# Background (non-blocking - you are notified when it finishes)
Bash(command: "node \"~/.claude/skills/codex-agent/scripts/codex-agent.mjs\" Your prompt here", run_in_background: true)
Background is preferred when launching multiple agents in parallel. Codex routinely takes 2-3x longer than Claude on the same brief.
Thin wrapper around the codex CLI for non-interactive use:
- Provide the prompt via arguments,
PROMPT_FILE, or stdin (briefs are byte-exact) - Model selection via
--modelorCODEX_MODEL - Session resume via
--resumeorCODEX_SESSION - Auto-detects OAuth login (
~/.codex/auth.json) or API keys - Clear diagnostics on failure
Prerequisites
- Node 18 or newer (
node --version) - Codex CLI v0.80.0+:
npm install -g @openai/codex@latest - Authentication, one of:
codex loginfor ChatGPT OAuth (creates~/.codex/auth.json)OPENAI_API_KEYenvironment variableCODEX_API_KEYenvironment variable (exec mode only)
Nothing else. The wrapper is a single Node script with no dependencies, so it
does not need bash, GNU grep -P, GNU sort -V, awk or sed. It runs the same
on Linux, macOS, WSL, and Windows (PowerShell, cmd, or Git Bash).
CODEX_HOME is honored if you have relocated your Codex configuration.
Usage
# Arguments
node "~/.claude/skills/codex-agent/scripts/codex-agent.mjs" Your prompt here
# File via env var (preferred for big briefs - byte-exact off stdin)
PROMPT_FILE=task.md node "~/.claude/skills/codex-agent/scripts/codex-agent.mjs"
# Stdin
cat task.md | node "~/.claude/skills/codex-agent/scripts/codex-agent.mjs"
What ships with it
1 file 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.
- 2d ago First seen · 158 lines · 84 tokens per session scan A 5034ea22bde7
codex-agent is a skill published in the GitHub repository TheSylvester/agentic-coding-tools (5 stars, last pushed 17d ago), licensed MIT. It adds 84 tokens to every session and 1,607 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.