jhcdevjhcdev/omc-codex/skills/codex-cli-runtime/SKILL.md

codex-cli-runtime

Skill2 starsChanged 8 months agoApache-2.0View on GitHub

Internal helper contract for calling the codex-companion runtime from Claude Code

3 other projects use a version of this, 1 of them edited.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Sep 2026Oct 2026Nov 2026

New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

JorgeMenaDev/skillstheir own version, first seen Oct 20, 2026
doctorplastic79-cmd/claude-skillsedited, first seen Oct 15, 2026
openai/codex-plugin-ccword for word, first seen Mar 30, 2026

Other versions3 projects use a version of this.
Word for word · 1
openai/codex-plugin-cc★ 33k100% same
Edited · 1
doctorplastic79-cmd/claude-skills★ 095% same
Wrote their own version · 1
JorgeMenaDev/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- codex-result-handlingSkill
- gpt-5-4-promptingSkill

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 3 are distinctive, and 13 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Use this skill only inside the codex:codex-rescue subagent.
line 9
Distinctive:
Prefer the helper over hand-rolled git, direct Codex CLI strings, or any other Bash activity.
line 16
Very specific:
Do not call setup, review, adversarial-review, status, result, or cancel from codex:codex-rescue.
line 17
Very specific:
Use task for every rescue request, including diagnosis, planning, research, and explicit fix requests.
line 18
Very specific:
Leave --effort unset unless the user explicitly requests a specific effort.
line 21
Very specific:
Leave model unset by default.
line 22
Very specific:
Default to a write-capable Codex run by adding --write unless the user explicitly asks for read-only behavior or only wants review, …
line 24
Very specific:
Use exactly one task invocation per rescue handoff.
line 27
Very specific:
If the forwarded request includes --background or --wait, treat that as Claude-side execution control only.
line 28
Very specific:
If the forwarded request includes --model, normalize spark to gpt-5.3-codex-spark and pass it through to task.
line 29
Very specific:
If the forwarded request includes --effort, pass it through to task.
line 30
Very specific:
If the forwarded request includes --resume, strip that token from the task text and add --resume-last.
line 31
Very specific:
If the forwarded request includes --fresh, strip that token from the task text and do not add --resume-last.
line 32
Very specific:
Default to write-capable Codex work in codex:codex-rescue unless the user explicitly asks for read-only behavior.
line 39
Distinctive:
Do not inspect the repository, read files, grep, monitor progress, poll status, fetch results, cancel jobs, summarize output, or do any …
line 41
Distinctive:
If the Bash call fails or Codex cannot be invoked, return nothing.
line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Codex Runtime

Use this skill only inside the codex:codex-rescue subagent.

Primary helper:

node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion.mjs" task "<raw arguments>"

Execution rules:

The rescue subagent is a forwarder, not an orchestrator. Its only job is to invoke task once and return that stdout unchanged.
Prefer the helper over hand-rolled git, direct Codex CLI strings, or any other Bash activity.
Do not call setup, review, adversarial-review, status, result, or cancel from codex:codex-rescue.
Use task for every rescue request, including diagnosis, planning, research, and explicit fix requests.
You may use the gpt-5-4-prompting skill to rewrite the user's request into a tighter Codex prompt before the single task call.
That prompt drafting is the only Claude-side work allowed. Do not inspect the repo, solve the task yourself, or add independent analysis outside the forwarded prompt text.
Leave --effort unset unless the user explicitly requests a specific effort.
Leave model unset by default. Add --model only when the user explicitly asks for one.
Map spark to --model gpt-5.3-codex-spark.
Default to a write-capable Codex run by adding --write unless the user explicitly asks for read-only behavior or only wants review, diagnosis, or research without edits.

Command selection:

Use exactly one task invocation per rescue handoff.
If the forwarded request includes --background or --wait, treat that as Claude-side execution control only. Strip it before calling task, and do not treat it as part of the natural-language task text.
If the forwarded request includes --model, normalize spark to gpt-5.3-codex-spark and pass it through to task.
If the forwarded request includes --effort, pass it through to task.
If the forwarded request includes --resume, strip that token from the task text and add --resume-last.
If the forwarded request includes --fresh, strip that token from the task text and do not add --resume-last.
--resume: always use task --resume-last, even if the request text is ambiguous.
--fresh: always use a fresh task run, even if the request sounds like a follow-up.
--effort: accepted values are none, minimal, low, medium, high, xhigh.
task --resume-last: internal helper for "keep going", "resume", "apply the top fix", or "dig deeper" after a previous rescue run.

Safety rules:

Default to write-capable Codex work in codex:codex-rescue unless the user explicitly asks for read-only behavior.
Preserve the user's task text as-is apart from stripping routing flags.
Do not inspect the repository, read files, grep, monitor progress, poll status, fetch results, cancel jobs, summarize output, or do any follow-up work of your own.
Return the stdout of the task command exactly as-is.
If the Bash call fails or Codex cannot be invoked, return nothing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free