agentleFS
Dianel555Dianel555/DSkills/skills/codex-cc/SKILL.md

codex-cc

Skill65 starsChanged 2 months agoMITView on GitHub

Delegates coding tasks from Codex to local Claude Code in print mode while preserving Claude's normal runtime customizations by default. Use when: (1) You want Codex to call Claude Code locally, (2) You need Claude-side skills, plugins, MCP servers, custom commands, CLAUDE.md rules, or workspace settings to stay active, (3) You want resumable Claude sessions from Codex via SESSION_ID, (4) You need thin `claude mcp` / `claude plugin` passthrough from the same bridge.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default execution uses claude -p and does not force --safe-mode, --bare, --disable-slash-commands, or --strict-mcp-config.

    line 18

≈ “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

Quick Start

python scripts/claude_bridge.py --cd "/path/to/project" --PROMPT "Analyze auth flow"

Output: JSON with success, SESSION_ID, agent_messages, stream_file (the raw Claude JSONL stream), and optional all_messages, stderr, or error.

Runtime Contract

  • Default execution uses claude -p and does not force --safe-mode, --bare, --disable-slash-commands, or --strict-mcp-config.
  • Claude Code therefore keeps its normal loading path for trusted-workspace customizations such as CLAUDE.md, skills, plugins, MCP servers, custom commands, and rules.
  • claude -p skips the interactive trust dialog and silently ignores invalid settings files, so use this only in workspaces you already trust and whose .claude settings already validate.
  • The bridge requests stream-json, persists each record immediately, and only treats Claude's final result record as a completed answer. Intermediate assistant records never mask a failed or incomplete turn.
  • On Windows the PROMPT is delivered through stdin when claude resolves to a .cmd/.bat shim, so the prompt never passes through cmd.exe quoting and cannot hit the command-line length limit.

Parameters

usage: claude_bridge.py [-h] --PROMPT PROMPT --cd CD [--SESSION_ID SESSION_ID]
                        [--model MODEL]
                        [--permission-mode {,acceptEdits,auto,bypassPermissions,manual,dontAsk,plan}]
                        [--dangerously-skip-permissions] [--timeout TIMEOUT]
                        [--stream-file STREAM_FILE] [--return-all-messages]
                        {mcp,plugin} ...

options:
  --PROMPT PROMPT                Instruction for the task to send to Claude Code.
  --cd CD                        Workspace root for Claude Code (cwd + --add-dir).
  --SESSION_ID SESSION_ID        Resume a conversation by session UUID.
  --model MODEL                  Claude model override. Aliases resolve against the active endpoint.
  --permission-mode ...          Claude permission mode override.
  --dangerously-skip-permissions Bypass Claude permission checks.
  --timeout TIMEOUT              Bridge-level timeout in seconds. Omit for no bridge deadline.
  --stream-file STREAM_FILE      Raw Claude stream-json JSONL destination.
  --return-all-messages          Include parsed stream records in the result.

subcommands:
  mcp                            Thin passthrough to `claude mcp`.
  plugin                         Thin passthrough to `claude plugin`.

Sessions

Capture SESSION_ID from the first successful response and reuse it for follow-ups. SESSION_ID is empty when a run never established a session (claude produced no stream output): resume only with an id the bridge actually returned.

# New Claude session
python scripts/claude_bridge.py --cd "/project" --PROMPT "Inspect failing tests"

# Resume the same Claude session
python scripts/claude_bridge.py --cd "/project" --SESSION_ID "uuid-from-response" --PROMPT "Now propose the fix"

Passthrough

python scripts/claude_bridge.py mcp list
python scripts/claude_bridge.py plugin list

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.