agentleFS
Sign inStart free
claude-worldclaude-world/director-mode-lite/skills/handoff-codex/SKILL.md

handoff-codex

Skill80 starsChanged 8 months agoMITView on GitHub

Continue a task in OpenAI Codex CLI through a portable Director handoff packet. Use when the user asks Codex to take over, wants an independent Codex implementation or review, or needs to preserve decisions and verification while changing CLIs.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Use the shared session-relay workflow.

    line 9
  2. Distinctive:

    Do not add bypass, approval, sandbox, or network flags as part of the handoff.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Handoff to Codex CLI

Use the shared session-relay workflow. Codex starts its own native session and reads a packet containing the goal, current state, decisions, Git evidence, verification, and next steps.

ROOT="${CLAUDE_PROJECT_DIR:-${GROK_WORKSPACE_ROOT:-}}"
[[ -n "$ROOT" ]] || ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
RELAY="$ROOT/.director-mode/bin/director-relay"
[[ -x "$RELAY" ]] || RELAY="$HOME/.claude/bin/director-relay"

"$RELAY" create \
  --from <claude|grok> --to codex \
  --goal "..." --summary "..." --next "..."

"$RELAY" continue --to codex

The second command prints the interactive codex invocation. Add --run only when the user wants it launched now. Use --headless when a one-shot codex exec continuation is appropriate.

Codex reads the repository's AGENTS.md, reusable skills from .agents/skills/, and generated agents from .codex/agents/. Confirm those surfaces with the installed CLI when debugging discovery.

Do not add bypass, approval, sandbox, or network flags as part of the handoff. Those controls belong to the Codex session and remain at their current native settings.

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