ultracodexlisted

# /ultracodex Keep ultracode's thoroughness; move the token-heavy work off metered Claude onto the cheaper Codex. **You (Opus) are the architect** — you emit the fewest tokens (judgment, specs, verdicts). Every token-heavy unit routes to a Codex worker via the helper. See the full design in `docs/DESIGN.md`. ## The worker helper Run one unit of work on the cheaper Codex lane: ``` bash ~/.claude/skills/ultracodex/codex-worker.sh "<task prompt>" [workdir] ``` - **ALWAYS go through this wrapper — never call the raw `~/bin/codex` shim (or a hand-rolled `codex exec`) directly.** The wrapper is where the service tier, the per-call `ULTRACODEX_MODEL`/`_EFFORT` overrides, the retry-once, the JSONL telemetry (`~/.claude/ultracodex-worker.log`), and the clean "final-message-only" output all live. Bypassing it means: no per-unit right-sizing, no retry, no visibility into WHY a call hung — you're left tailing a temp file and guessing. The raw shim exists only as a PATH passthrough for interactive use; it is NOT the orchestration path. - Resolves the Codex binary dynamically, runs `codex exec`, prints ONLY the worker's final message. Exit 0 = success. - On failure/timeout/binary-missing it prints a line starting `ULTRACODEX_WORKER_ERROR:` and exits non-zero → that is your signal to run the **Codex-down fallback** (below). - Run workers in PARALLEL by issuing multiple Bash calls in one turn. ### Large fan-out (research, bulk lookups) — spawn as many as you need The