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-statusnpx skills add LeeJuOh/claude-code-zero --skill codex-statusgit 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.00041 | $0.00603 |
| Opus 5 | $0.00020 | $0.00302 |
| Sonnet 5 | $0.00008 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
codex-status 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Job Status + Stored Reviews
Thin wrapper around the Official Codex companion's status subcommand, combined with a listing of review files saved by codex-advisor. Useful when the user has disabled the Official plugin's slash commands but still wants job visibility.
Phase 1: Invoke companion status
set -o pipefail
CODEX_COMPANION=$("${CLAUDE_PLUGIN_ROOT}/scripts/resolve-companion.sh") \
|| { echo "Official Codex plugin not found — run /codex-setup" >&2; exit 1; }
# Forward args verbatim. The companion handles [job-id], --wait,
# --timeout-ms, --all, and prints a markdown table.
node "$CODEX_COMPANION" status $ARGUMENTS
Relay the companion's output verbatim. Do NOT reformat — the companion already renders a compact table.
Phase 2: List stored review files
Codex-advisor writes reports to ${CLAUDE_PLUGIN_DATA}/reviews/. Add a short section listing the most recent files so the user can correlate jobs with saved reports:
REVIEWS_DIR="${CLAUDE_PLUGIN_DATA}/reviews"
if [ -d "$REVIEWS_DIR" ]; then
ls -1t "$REVIEWS_DIR" 2>/dev/null | head -10
fi
Format:
## Recent codex-advisor reports
- review-20260414-102530.md
- rescue-20260414-100112.md
- ...
Location: ${CLAUDE_PLUGIN_DATA}/reviews/
If the directory doesn't exist yet, skip the section (don't create it).
Gotchas
- Don't reformat the companion's table. Its markdown is already compact; reformatting risks dropping columns.
--waitblocks up to--timeout-ms(default 240000 = 4 min). If the user passes--waiton a running job, surface a "blocking for up to N seconds" note so they aren't surprised by the pause.--allincludes completed jobs across sessions. Without it, status shows only the current workspace's jobs.- Stored reports and companion jobs are not 1:1. A job that failed before codex-advisor's Phase 5 has no report; a review-<ts>-failed.md corresponds to a companion job that completed with an error. Don't assert matching.
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 · 57 lines · 41 tokens per session scan A 1f34005f1aed
codex-status is a skill published in the GitHub repository LeeJuOh/claude-code-zero (51 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 603 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…