Agent skill · AI & Agents

codex-cli-bridge

Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools

Alireza Rezvani23,369★ · +428/wk · 1 repos on radarProfile →
codexclaude-codeships scriptsMIT
Install
npx skills add alirezarezvani/claude-code-skill-factory --skill codex-cli-bridge --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 15
SKILL.md size: 9 KB
Bundled scripts: yes
Path: generated-skills/codex-cli-bridge/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 839
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Codex CLI Bridge Skill ## Purpose This skill creates a comprehensive bridge between **Claude Code** and **OpenAI's Codex CLI**, enabling seamless interoperability through: 1. **Documentation Translation**: Converts CLAUDE.md → AGENTS.md (reference-based, no file duplication) 2. **Execution Helpers**: Python wrappers for Codex CLI commands (always uses `codex exec`) 3. **Skill Documentation**: Makes Claude Skills accessible to Codex CLI users ## Key Capabilities ### 1. CLAUDE.md → AGENTS.md Generation - Parses CLAUDE.md and project structure - Scans `.claude/skills/`, `.claude/agents/`, `documentation/` folders - Generates comprehensive AGENTS.md with file path references - **Reference-based**: No file duplication, only links to existing files - Documents Skills with most relevant usage method (bash scripts vs prompt references) ### 2. Safety Mechanism - **Auto-checks Codex CLI installation** (`codex --version`) - **Auto-runs `/init`** if CLAUDE.md missing (with user notification) - Validates authentication and environment - User-friendly error messages ### 3. Codex CLI Execution Helpers - `exec_analysis()` - Read-only analysis tasks (gpt-5, read-only sandbox) - `exec_edit()` - Co

What's inside
Steps it walks through
  1. Purpose
  2. Key Capabilities
  3. 1. CLAUDE.md → AGENTS.md Generation
  4. 2. Safety Mechanism
  5. 3. Codex CLI Execution Helpers
  6. 4. Skill Documentation for Codex CLI
  7. Input Requirements
  8. For AGENTS.md Generation
  9. For Codex Execution
  10. Output Formats
  11. AGENTS.md Structure
  12. Execution Helper Output
  13. Python Scripts
  14. safetymechanism.py
Ships with 14 files
  • CHANGELOG.md
  • HOW_TO_USE.md
  • INSTALL.md
  • README.md
  • agents_md_generator.py
  • bridge.py
  • claude_parser.py
  • codex_executor.py
  • expected_output.json
  • package.sh
  • project_analyzer.py
  • safety_mechanism.py
  • sample_input.json
  • skill_documenter.py
Commands it runs
codex exec -m gpt-5 -s read-only \
codex exec -m gpt-5-codex -s workspace-write \
codex exec resume --last
codex --version  # Should show v0.48.0 or higher
codex login
cp -r generated-skills/codex-cli-bridge ~/.claude/skills/
Skill auto-discovered when Claude Code loads this project
which codex  # Should return path
codex --version  # Should work
Manually run /init
More from claude-code-skill-factory
All skills →
About this skill
What does the codex-cli-bridge skill do?

Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools

How do I install it?

Run `npx skills add alirezarezvani/claude-code-skill-factory --skill codex-cli-bridge --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From alirezarezvani/claude-code-skill-factory, a repository with 839 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going