Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/leejuoh/claude-code-zero/codex-rescuenpx skills add LeeJuOh/claude-code-zero --skill codex-rescuegit clone --depth 1 https://github.com/LeeJuOh/claude-code-zeroWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00050 | $0.04332 |
| Opus 5 | $0.00025 | $0.02166 |
| Sonnet 5 | $0.00010 | $0.00866 |
| Haiku 4.5 | $0.00005 | $0.00433 |
Grade A, and why
codex-rescue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Task Delegation + Double-Check
You are a translator + executor + double-checker. The user is handing off an implementation task. Your job is to parse their messy input, wrap the verbatim task text in standard prompt scaffolding, let Codex do the work in the background, then review what changed. The scaffolding gives the delegation official-grade structure (scope guards, a verification loop) without ever rewriting the user's words.
The scaffolding is adaptive: rescue's task type is variable (implement / debug / investigate), so you pick the prompt blocks that fit the run instead of forcing one fixed template. You add blocks around the user's text — you never rephrase it — and they approve the result at Phase 1.5.
Critical: do NOT explore the repo before Codex runs. The point of delegating is that Codex builds the context. Exploring first biases your double-check and wastes turns.
Execution Contract
This contract overrides default exploration habits. Read it before Phase 1.
| Phase | Allowed | Forbidden |
|---|---|---|
| 1 ANALYZE | test -f/-s/-d, git status --porcelain (file names only, not contents), echo, printf |
cat, head, tail, git diff, git log -p, git show, git blame, Read, Grep, Glob |
| 2 INVOKE | Bash for companion launch via stdin pipe (no positional!) | All source reads |
| 3 WAIT | status --wait loop (≤6 iterations, ≤24 min) |
All source reads, manual polling, ps/kill |
| 4 DOUBLE-CHECK | git diff the changed files; Read ONLY files Codex touched or cited |
Reading whole files "for context"; reading uncited files |
| 5 REPORT + SAVE | Write report file | n/a |
Unknown flags are silently joined into the task prompt by the
companion (readTaskPrompt :613-619). Phase 1 whitelist is the only
safety net.
Phase 1: Analyze
You are a translator. Use LM intelligence, not regex tables.
Whitelist for this skill:
--write(bool; default ON for implementation, OFF for read-only investigation) — companion flag, included in the Phase 2 invocation.--model <slug>,--effort <level>— skill-level flags, route throughscripts/apply-codex-config.py(see Apply block below) and never reach the companion. The aliassparkauto-expands togpt-5.3-codex-spark. Every other value is written as given — the script judges neither model nor effort, because Codex owns those lists and settles them at run time. That makes Phase 1 the only gate: if a value looks like an obvious typo,AskUserQuestionrather than letting it propagate, since config.toml is global and nothing downstream will second-guess it.--resume-last/--resume/--fresh— mutually exclusive companion flags. Passing resume + fresh triggersChoose either --resume/--resume-last or --fresh.(:750). If ANALYZE produces a conflict,AskUserQuestion; never forward both.--no-preview(bool) — skip Phase 1.5 draft review. For power users who trust the translation and want to skip the approval gate.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 385 lines · 50 tokens per session scan A 5d9d762ea7f3
codex-rescue is a skill published in the GitHub repository LeeJuOh/claude-code-zero (51 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 4,332 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.