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/iml1s/agent-cli-skills/codex-cli-agentnpx skills add ImL1s/agent-cli-skills --skill codex-cli-agentgit clone --depth 1 https://github.com/ImL1s/agent-cli-skillsWhat 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.00090 | $0.00661 |
| Opus 5 | $0.00045 | $0.00331 |
| Sonnet 5 | $0.00018 | $0.00132 |
| Haiku 4.5 | $0.00009 | $0.00066 |
Grade A, and why
codex-cli-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.
What it actually says
Codex CLI (codex exec) Executor
When to use
- User wants Codex /
codex execas the coding agent - Need Codex subagents, agent TOML profiles, or CSV fan-out
- Sandboxed writes (
-s workspace-write) vs strict read-only reviews (-r)
Wrapper
./codex-exec.sh -C /path/to/repo -s workspace-write "Implement X. NO git."
./codex-exec.sh -r -C /path/to/repo "Review for bugs" # sandbox read-only
./codex-exec.sh -T -C /path/to/repo "Parallelize with subagents"
./codex-exec.sh -j -o /tmp/last.txt -f /tmp/bundle.txt
./codex-exec.sh --enable some_feature -m <model> "…"
Flags: -m · -t · -C · -s read-only|workspace-write|danger-full-access · -o last-message file ·
-f · -j/--json · -r · -T · --skip-git-repo-check (default on) · --require-git-repo ·
--ephemeral · --add-dir · --image · --enable · --profile · --no-git · -- passthrough.
-C is absolutized before use (avoids nested relative cwd).
Sandbox vs writing answer files
If the prompt must write a file under the workspace, do not use -r / read-only.
That fails with writing is blocked by read-only sandbox after the model finishes reasoning.
Use -s workspace-write and instruct “only write the designated path”, or capture stdout.
Native multi-agent
- Subagents (parallel spawn + synthesize); custom roles in
~/.codex/agents/*.tomlor.codex/agents/ - Experimental batch:
spawn_agents_on_csv(one worker per CSV row) - Feature flags:
codex features list|enable|disable -Tasks Codex to prefer subagents / CSV fan-out when useful
Models
Do not hard-code a stale model table. Discover via your Codex build / account docs.
Pin with -m when automation requires stability.
Discipline
Always --skip-git-repo-check outside git repos. Exit code untrusted. Orchestrator owns git.
What ships with it
4 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.
- 2d ago First seen · 55 lines · 90 tokens per session scan A 5b51a78b632c
codex-cli-agent is a skill published in the GitHub repository ImL1s/agent-cli-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 661 once invoked, about $0.0005 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
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
parallel-debugging
Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.
observal-registry
Searches, recommends, bulk-submits, installs, edits, versions, archives, restores, transfers, and manages co-authors for Observal MCP servers, skills, hooks, prompts, and sandboxes. Use when the user wants to find components, publish one or many they control, install them into a harness, or manage their lifecycle.
test-writer
name: test-writer description: Generates comprehensive unit tests for code version: 1.0.0 owner: example tasktype: testing.
agent-desktop
Use the built-in Computer sub-agent with agent-desktop for macOS desktop automation. Apply when a task needs application launching, accessibility snapshots, stable element refs, window focusing, semantic clicks/typing, or visual confirmation outside the browser sandbox.