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-researchnpx skills add LeeJuOh/claude-code-zero --skill codex-researchgit 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.00048 | $0.03453 |
| Opus 5 | $0.00024 | $0.01726 |
| Sonnet 5 | $0.00010 | $0.00691 |
| Haiku 4.5 | $0.00005 | $0.00345 |
Grade A, and why
codex-research 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Research + Cross-Model Synthesis
You are a translator + executor + double-checker. The user wants deep-dive research. Your job is to hand the topic (and any context document) to Codex without loading the document into your own context, then synthesize Codex's findings with your own independent analysis.
For code review use /codex-review. For plan verification use
/codex-verify.
Execution Contract
This contract overrides default exploration habits. Read it before Phase 1.
| Phase | Allowed | Forbidden |
|---|---|---|
| 1 ANALYZE | test -f/-s, wc -l/-c, file, echo, printf, cat "$DOC" >> "$PROMPT_FILE" (file-redirect, no stdout) |
cat "$DOC" to stdout, head, tail, Read, Grep, Glob |
| 2 INVOKE | Bash for companion launch via stdin pipe | All source / document reads to stdout |
| 3 WAIT | status --wait loop (≤6 iterations, ≤24 min) |
All reads, manual polling, ps/kill |
| 4 DOUBLE-CHECK | Verify claims against your own knowledge; read the context document (if any) now | n/a |
| 5 REPORT + SAVE | Write report file | n/a |
Why the document stays out of context in Phase 1-3: same reason as verify — independence. If you read it upfront, your synthesis just echoes Codex instead of adding independent perspective.
Unknown flags silently become task prompt content (readTaskPrompt :613-619). Phase 1 is the only safety net.
Phase 1: Analyze + assemble blind payload
Parse $ARGUMENTS
Whitelist for this skill: --model <slug>, --effort <level> (skill-level, route through apply-codex-config.py — never reach the companion). The topic and optional document path are other skill inputs, not companion flags.
Rules:
- Plain text → treat as the research topic/question.
- A single path → treat as a context document; the research task comes from the surrounding text or the filename.
resume [follow-up]→ pass--resume-lastto the companion.- Mixed (topic + path) → both, in the blind payload template.
- Meta-instructions addressed to YOU (e.g. "in Korean", "quickly", "thoroughly" — often typed in the user's own language) → obey for your own behavior, never include in the prompt.
- No args →
AskUserQuestion: "What should I research?" - Unknown flags (e.g.,
--base,--write,--foo) →AskUserQuestion. research has no companion flags to forward.--model/--effortare the only skill-level flags and route throughapply-codex-config.py, not the companion. --no-preview→ skip Phase 1.5 draft review. Power users who trust the translation.
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 · 368 lines · 48 tokens per session scan A 296e1f31a7f1
codex-research is a skill published in the GitHub repository LeeJuOh/claude-code-zero (51 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 3,453 once invoked, about $0.0002 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…