How do I install the Codex Control skill?

Run npx skillmds@latest add newkayak12/codex-control in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Codex Control skill do?

Use when a harness stage must delegate Implement or Test work to local Codex CLI from plugin, repo-local, or embedded installs. It is listed under Coding & Dev Tools on SkillMD.

Is Codex Control safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Codex Control?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Codex Control free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Codex Control?

newkayak12 (@newkayak12) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Codex Control by newkayak12 — Agent Skill

Name: Codex Control
Author: newkayak12

File contents

codex-control

Resolve and run the harness Codex CLI bridge without assuming the project embedded .claude/harness/**.

Adapter Resolution

Use the first existing codex-exec-adapter.mjs path:

Explicit codex_adapter_path from the Workflow args, when provided.
Project-local repo layout: harness/engine/codex-exec-adapter.mjs.
Embedded install layout: .claude/harness/engine/codex-exec-adapter.mjs.
Plugin-mode layout: read the project's CLAUDE.md Harness block, find the Workflow({ scriptPath: "<harness plugin root>/engine/pipeline.js", ... }) example, and derive <harness plugin root>/engine/codex-exec-adapter.mjs.

If none exists, record that Codex was unavailable and continue through the normal Claude/Sonnet path.

Run Contract

Always run node "$ADAPTER" --detect --cwd "$PWD" --output <providers.json> before asking Codex to implement or verify.
Use a separate Codex process for Implement and Test.
Implement may use --sandbox workspace-write.
Test prompts must be verification-only: do not ask Codex to change implementation files, and do not trust the Implement narrative without command/file evidence.
After Codex returns, read the adapter JSON and produce the normal harness artifact shape expected by the current stage.

Frequently asked questions

Codex Control