Dual-AI code analysis pairing OpenAI Codex with Claude code-searcher — the lightest consult variant, two citation-verified perspectives. Use for a quick second opinion on a code question.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Dual-AI code analysis pairing OpenAI Codex with Claude code-searcher — the lightest consult variant, two citation-verified perspectives. Use for a quick second opinion on a code question.
Dual-AI Consultation: Codex vs Code-Searcher
You orchestrate consultation between OpenAI's Codex and Claude's code-searcher to provide comprehensive analysis with comparison.
Finding specific implementations across a codebase
Lower value (single AI may suffice):
Simple syntax questions
Basic file lookups
Straightforward documentation queries
Workflow
When the user asks a code question:
1. Build Enhanced Prompt
Problem-restate pre-flight (non-blocking). Before building the prompt, emit ONE line
restating the code question you are about to dispatch (and, only if genuinely ambiguous, the
alternative reading), then proceed:
Reading this as: «one-line restatement» (alt: «other reading», if any) — proceeding to consult; interrupt now to correct the framing.
Emit-and-proceed — do not ask-and-wait (the orchestrator can't reliably detect its own
misframing). One line, and it guards the whole dispatch against a wrong-framing run.
Wrap the user's question with structured output requirements:
[USER_QUESTION]
=== Analysis Guidelines ===
**Structure your response with:**
1. **Summary:** 2-3 sentence overview
2. **Key Findings:** bullet points of discoveries
3. **Evidence:** file paths with line numbers (format: `file:line` or `file:start-end`)
4. **Confidence:** High/Medium/Low with reasoning
5. **Limitations:** what couldn't be determined
**Line Number Requirements:**
- ALWAYS include specific line numbers when referencing code
- Use format: `path/to/file.ext:42` or `path/to/file.ext:42-58`
- For multiple references: list each on a SEPARATE line with its own file path
(avoid comma-separated multi-citation like `file.ts:45, 67, 98`)
- Include brief code snippets for key findings
**Examples of good citations:**
- "The authentication check at `src/auth/validate.ts:127-134`"
- "Configuration loaded from `config/settings.json:15`"
- "Error handling in `lib/errors.ts:45`, `lib/errors.ts:67-72`, and `lib/errors.ts:98`"
**Citations Index (required):** end your response with a fenced block, one line per
Key Finding (repeat each block entry's `file:line` inline in the finding as usual):
```citations
<finding #> — path/to/file.ext:LINE[-END]
```
Severity / no-manufacture block — ORCHESTRATOR-GATED. Append the block below to both
agents' prompts identically ONLY when the query is a defect hunt / code review (bug,
security audit, "what's wrong with…", "review this"). OMIT it for explanatory / "how does
X work" questions, where "found nothing" is not meaningful. The orchestrator — which knows
the query type — makes this include/omit decision once, BEFORE writing the prompt files;
do not leave it to each agent to self-classify. When included, append exactly these two
bullets (the text only — no leading marker):
- Tag each finding with a **Severity** — Critical (wrong/broken on expected inputs) · Warning (fails on unusual but valid inputs) · Info (noteworthy, not actionable). Severity is *impact*, orthogonal to the Confidence field (*certainty*).
- **Finding nothing is a valid, valuable result.** If the code is correct, say so plainly with one verifying note — do NOT manufacture issues to look thorough.
2. Invoke Both Analyses in Parallel
Setup (run first).$CLAUDE_PROJECT_DIR is not always exported into the Bash
tool shell, so resolve it with a $PWD fallback and ensure the tmp dir exists.
Substitute the resolved literal path for $PROJECT_DIR, and a freshly generated
RUN_ID (seconds-resolution + 4-char nonce, e.g. run-2026-05-25-143052-a7f3),
into every command below. The RUN_ID in temp filenames prevents collisions
between two concurrent invocations sharing $PROJECT_DIR/tmp.
PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$PWD}"# Validate BEFORE creating tmp — `mkdir -p` would otherwise make the check pass even# for a bad path (it creates the dir, then `[ -d ]` always succeeds).
[ -d "$PROJECT_DIR" ] || { echo"ERROR: PROJECT_DIR '$PROJECT_DIR' is not a directory" >&2; exit 1; }
mkdir -p "$PROJECT_DIR/tmp"# Pre-flight (fail fast, not after a 10-min hang). jq is a HARD dependency — output# parsing needs it — so abort now rather than warn-and-continue into opaque failures.command -v jq >/dev/null 2>&1 || { echo"ERROR: 'jq' not found — required for output parsing; aborting" >&2; exit 1; }
# codex is a soft dependency — the CODEX_BIN resilience block below resolves or SKIPs it.command -v codex >/dev/null 2>&1 || \
zsh -i -c "type codex" >/dev/null 2>&1 || \
bash -i -c "type codex" >/dev/null 2>&1 || \
echo"WARNING: 'codex' not found — will attempt nvm resolution below, else SKIP"# Sweep stale orphans (>60 min) from crashed prior runs (best-effort, age-based —# can theoretically delete a live run's files if it paused >60 min; acceptable).
find "$PROJECT_DIR/tmp" -maxdepth 1 -name '*-prompt-*.txt' -mmin +60 -delete 2>/dev/null
find "$PROJECT_DIR/tmp" -maxdepth 1 -name '*-output-*.jsonl' -mmin +60 -delete 2>/dev/null
Codex binary resilience (run once, before dispatch). An nvm-managed codex
can be a symlink whose @openai/codex install is broken (deleted vendor binary →
spawn ... ENOENT), and a broken version can sit EARLIER on PATH than a working
one. command -v / zsh -i return the broken path, so detect by RUNNING the
binary. If the PATH-resolved codex fails, hunt all nvm node installs for one whose
--version succeeds and emit its absolute path. Emit CODEX_BIN=SKIP if none work.
CODEX_BIN=""; INTERACTIVE_SHELL=zsh
# Capture WHICH interactive shell resolves codex (nvm may be in only one of# ~/.zshrc / ~/.bashrc). The dispatch below uses $INTERACTIVE_SHELL so a# .bashrc-only setup on macOS still works (prior bug: probe accepted bash,# dispatch hardcoded zsh).if zsh -i -c 'codex --version' >/dev/null 2>&1; then CODEX_BIN="codex"; INTERACTIVE_SHELL=zsh # codex resolves via zshelif bash -i -c 'codex --version' >/dev/null 2>&1; then CODEX_BIN="codex"; INTERACTIVE_SHELL=bash # codex resolves via bashelse# Match symlinks too (-type l): nvm/npm install codex as a bin/ symlink, which -type f misses.
CODEX_BIN=$(find "$HOME/.nvm/versions/node" -maxdepth 5 -name codex \( -type f -o -type l \) 2>/dev/null | while IFS= read -r p; do"$p" --version >/dev/null 2>&1 && { printf'%s\n'"$p"; break; }
done)
[ -z "$CODEX_BIN" ] && CODEX_BIN="SKIP"fiecho"CODEX_BIN=$CODEX_BIN"# MUST echo: shell vars don't persist across Bash tool callsecho"INTERACTIVE_SHELL=$INTERACTIVE_SHELL"# the interactive shell that resolves codex; substitute into the dispatch below# Resolve the timeout binary used to wrap the Codex gen dispatch (§Step 2 below) so a# hung CLI is bounded rather than running unbounded — the harness may auto-background# the dispatch, letting it escape the Bash tool's own timeout. Probe BOTH names:# Homebrew coreutils installs GNU timeout as `gtimeout`; plain `timeout` exists only# when the coreutils gnubin PATH is on. If neither exists, TIMEOUT_CMD stays empty and# the dispatch runs UNWRAPPED (best-effort Bash-tool timeout; `brew install coreutils`# restores the hard guard).
TIMEOUT_CMD=""ifcommand -v timeout >/dev/null 2>&1; then TIMEOUT_CMD="timeout"elifcommand -v gtimeout >/dev/null 2>&1; then TIMEOUT_CMD="gtimeout"fiecho"TIMEOUT_CMD=$TIMEOUT_CMD"# substitute into the §Step-2 Codex dispatch (when empty: omit the wrap)
Two-phase dispatch (required). Tool calls in one message run concurrently, so emitting the Codex prompt-file Write and the Codex dispatch together races the dispatch ahead of the file (Codex errors on a missing prompt file). Use two messages: message 1 writes the Codex prompt file (Step 1 below); message 2 issues the Codex dispatch (Step 2) and the Code-Searcher Agent call in parallel:
Gen-dispatch timeout watchdog (GEN_TIMEOUT=1200). Each $TIMEOUT_CMD -k 10 1200-prefixed CLI gen below — SIGTERM at 1200s (20 min), SIGKILL 10s later (-k 10, which also reaps orphaned Node/MCP children) — is bounded against a hung provider CLI that would otherwise run unbounded (the harness may auto-background the dispatch, so the Bash tool's own timeout is not a reliable cap). When TIMEOUT_CMD is empty (no timeout/gtimeout): omit the $TIMEOUT_CMD -k 10 1200 prefix and dispatch unwrapped (the existing §Setup fallback) — set the Bash tool's own timeout parameter to 1300000 ms as a best-effort cap, and brew install coreutils to restore the hard guard. On a timed-out gen (exit 124 = SIGTERM, 137 = SIGKILL): the output file is empty/truncated, so the existing [ -z … ] parse guard already drops the agent — additionally surface Agent X timed out after 1200s (distinct from an auth failure, which leaves non-empty stderr) and re-count against the §Setup minimum-agent guard. Do not retry. Code-Searcher (Agent tool) carries no$TIMEOUT_CMD -k 10 1200 prefix — it is bounded by its own mechanism, not this watchdog.
For Codex:
Model ownership — the model is CONFIG-OWNED, never named by this skill.
Do not pass -m: inherit the model and reasoning effort from Codex configuration
(~/.codex/config.toml — this installation is configured for gpt-5.6-sol, high effort).
Report the agent as plain "Codex" everywhere in the report; never a hardcoded version
string. A hardcoded label silently misreports the model the moment the config changes:
this skill advertised GPT-5.6-terra in seven places while every dispatch had been
running gpt-5.6-sol, because the dispatch carries no -m and never did (corrected
2026-08-01).
Step 1: Write the enhanced prompt to a temp file using the Write tool:
Write to $PROJECT_DIR/tmp/codex-prompt-RUN_ID.txt with the ENHANCED_PROMPT content
Step 2: Execute Codex (allow ~10 min; Codex can be slow). Pipe the prompt
via stdin and capture the JSONL event stream to a file.
Pick the form based on CODEX_BIN from Setup:
CODEX_BIN=codex → use the interactive-shell form below ($INTERACTIVE_SHELL resolved in Setup).
CODEX_BIN is an absolute path → use the absolute-path form (calls the
binary directly so PATH ordering can't shadow it again).
CODEX_BIN=SKIP → no working codex; skip this dispatch, present only the
Code-Searcher response. Label the report a degraded single-AI run — Code-Searcher is
the sole agent, so there is no cross-comparison — and note that a direct Read or a lighter
path would have been cheaper. Record the skip in §4 (error handling) / §5 (comparison report).
macOS/Linux (CODEX_BIN=codex; $INTERACTIVE_SHELL = the zsh|bash literal resolved in Setup):
Why this exact form (each piece prevents a failure seen in practice):
-s read-only is the portable Codex sandbox flag — it needs no
~/.codex/config.toml[profiles.readonly] entry, unlike -p readonly
(which silently misbehaves when that profile is absent).
stdin pipe (cat … | …) instead of "$(cat …)" avoids the
Reading additional input from stdin... hang (Codex waits on stdin when the
prompt is passed as a positional) and ARG_MAX limits on large prompts.
-C '$PROJECT_DIR' — outer-shell single-quote expansion of an absolute
path — gives Codex project context. Do NOT pass the dir via an inner-shell
positional (-C "$0"/literal placeholders): besides being fragile, a skill
loaded WITH user arguments has its $0/$1/$2 rewritten by Claude Code's
argument substitution, so a wrong-bound $0 produces a cryptic
Error: No such file or directory (os error 2).
Parse $PROJECT_DIR/tmp/codex-output-RUN_ID.jsonl with the §2a recipes.
For Code-Searcher: Use Agent tool with subagent_type: "code-searcher" with the same enhanced prompt (plus the orchestrator-gated Severity block above on defect-hunt runs)
No sub-agent fan-out — append this VERBATIM to the code-searcher prompt: "Do this analysis YOURSELF — do NOT spawn sub-agents. Do not use the Agent/Task tool to fan out to code-searcher, Explore, general-purpose, or any other subagent; use Read/Grep/Glob/Bash directly, however many calls that takes." Code-searcher runs with all tools and fans out unprompted on Sonnet 5 (reported live 2026-08-01); a sub-agent inherits none of this run's constraints, and the Agent-tool call carries no dispatch watchdog — a stalled fan-out underneath it stalls the whole consult. (consult-panel §1d carries the full form of this guard.)
This parallel execution significantly improves response time.
2a. Parse Codex --json Output Files (jq Recipes)
Codex CLI with --json typically emits newline-delimited JSON events (JSONL). Some environments may prefix lines with terminal escape sequences; these recipes strip everything before the first { and then fromjson? safely.
Set a variable first:
FILE="$PROJECT_DIR/tmp/codex-output-RUN_ID.jsonl"# the file the §2 dispatch redirected to
This prevents stale prompts from accumulating and avoids potential confusion in future runs.
4. Handle Errors
If one agent fails or times out, still present the successful agent's response
Note the failure in the comparison: "Agent X failed to respond: [error message]"
Provide analysis based on the available response
5. Create Comparison Analysis
Use this exact format:
Codex Response
[Raw output from codex-cli agent]
Code-Searcher (Claude) Response
[Raw output from code-searcher agent]
Comparison Table
(MANDATORY — always render this table on a multi-agent run; it is the at-a-glance visual diff readers rely on, so never skip it. Omit only in a degraded single-AI run, where there is nothing to compare.)
Aspect
Codex
Code-Searcher (Claude)
File paths
[Specific/Generic/None]
[Specific/Generic/None]
Line numbers
[Provided/Missing]
[Provided/Missing]
Code snippets
[Yes/No + details]
[Yes/No + details]
Unique findings
[List any]
[List any]
Accuracy
[Note discrepancies]
[Note discrepancies]
Strengths
[Summary]
[Summary]
Agreement Level
High Agreement: Both AIs reached similar conclusions - Higher confidence in findings
Partial Agreement: Some overlap with unique findings - Investigate differences
Bucket each distinct finding by how many agents independently reached it:
Corroborated — both agents report it. Highest trust as a consensus signal — this
dual has no citation-verification stage, so it is agreement, not verified correctness.
Solo — reported by one agent only. Plausible but unconfirmed.
Disputed — the agents contradict on the point. Flag for manual verification.
(Cluster findings across agents by their claim + file:line — the Citations Index blocks
make this pairing mechanical. On a defect-hunt run, tag each listed finding with its
agent-assigned Severity — Critical/Warning/Info.)
