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-transfernpx skills add LeeJuOh/claude-code-zero --skill codex-transfergit 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.00086 | $0.01496 |
| Opus 5 | $0.00043 | $0.00748 |
| Sonnet 5 | $0.00017 | $0.00299 |
| Haiku 4.5 | $0.00009 | $0.00150 |
Grade A, and why
codex-transfer 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Session Transfer
One-way handoff. Unlike every other codex-advisor skill, there is no double-check phase — once the transfer completes, work continues in Codex outside Claude Code, so there is nothing left here to classify. The wrapper's job is whitelisting, error taxonomy, and disable-parity — not verification.
Phase 1: Analyze
Whitelist for this skill: --source <path>, --json. Nothing else
— transfer has no prompt, so there is no focus text or model/effort to
route.
--source <path>— explicit Claude session.jsonlto import. Optional; when omitted the companion falls back to theCODEX_COMPANION_TRANSCRIPT_PATHenv var, which codex-advisor's own SessionStart hook (hooks/session-start.mjs) sets automatically — whether or not the Official plugin itself is enabled.--json— when the user passes this, show them the raw JSON payload in Phase 3 instead of the friendly summary. This is independent of the--jsoncodex-advisor always adds internally to the companion call (see Phase 2) — that one is for our own parsing, not the user's request.- Unrecognized token (any other flag, or free-standing text) →
AskUserQuestion. Transfer has no positional argument — the companion silently discards anything it doesn't recognize as--source/--cwd/--json(handleTransferdestructures onlyoptions, neverpositionals), so passing it through would do nothing rather than corrupt a prompt. Still don't forward it: ask what the user meant. If it looks like a task description, suggest/codex-rescueinstead — transfer moves the whole session, it doesn't run a task.
Phase 2: Invoke
Single synchronous call — no --wait/--background, no Pattern A/B.
The companion's own import timeout is 2 minutes
(EXTERNAL_AGENT_IMPORT_TIMEOUT_MS, lib/codex.mjs:52), so give the
Bash tool call itself a timeout comfortably above that (e.g.
150000) — a shorter tool-side timeout could kill the process right at
the companion's own deadline and mask its real error message.
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 · 89 lines · 86 tokens per session scan A 6087728ddf87
codex-transfer is a skill published in the GitHub repository LeeJuOh/claude-code-zero (51 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 1,496 once invoked, about $0.0004 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.