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 skills add sd0xdev/sd0x-harness --skill codex-cli-reviewgit clone --depth 1 https://github.com/sd0xdev/sd0x-harnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sd0xdev/sd0x-harness/codex-cli-review)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/codex-cli-review"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/codex-cli-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/codex-cli-review"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/codex-cli-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00063 | $0.00909 |
| Opus 5.5 | $0.00025 | $0.00364 |
| Sonnet 5.5 | $0.00013 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
codex-cli-review 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 1mo 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex CLI Review Skill
Trigger
- Keywords: codex cli review, cli review, script review
When to Use
- Need Codex to independently explore the entire project (full disk read)
- Don't need MCP's context persistence feature
- Want to use Codex CLI's native review format
When NOT to Use
- Need iterative review (use
/codex-review-fast --continue) - Need to follow up with Codex (use MCP version)
- Only want to see diff without waiting for Codex exploration (use
/codex-review-fast)
Difference from MCP Version
| Feature | CLI Version (this skill) | MCP Version |
|---|---|---|
| Independent explore | Full disk read | Needs explicit instruction |
| Context persistence | None | threadId |
| Iterative review | Each run independent | --continue |
| Format | Codex native format | Custom prompt format |
| Execution method | Script invocation | MCP tool invocation |
Workflow
┌─────────────────────────────────────────────────────────────────┐
│ Step 1: Check Changes │
├─────────────────────────────────────────────────────────────────┤
│ git status --porcelain │
│ No changes -> Early exit │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Step 2: Execute Codex CLI │
├─────────────────────────────────────────────────────────────────┤
│ codex review --uncommitted │
│ -c 'sandbox_permissions=["disk-full-read-access"]' │
│ │
│ Codex will independently: │
│ - Read changed files │
│ - Explore related dependencies │
│ - Check existing tests │
│ - Understand project structure │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Step 3: Output Review Results │
├─────────────────────────────────────────────────────────────────┤
│ Codex native format: │
│ - Summary │
│ - Issues (Critical/Major/Minor/Suggestion) │
│ - Recommendations │
└─────────────────────────────────────────────────────────────────┘
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 134 lines · 63 tokens per session scan A 082bf9819762
codex-cli-review is a skill published in the GitHub repository sd0xdev/sd0x-harness (194 stars, last pushed 10d ago), licensed MIT. It adds 63 tokens to every session and 909 once invoked, about $0.0003 per session on Opus 5.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
code-review
Two-mode skill: (1) adversarial review — spec compliance + code quality + security, confidence-scored findings with file:line evidence; (2) receiving review — verify-before- agreeing discipline for acting on external/human review feedback.
codebase-hygiene
Two-mode skill: (1) find semantic duplicates — functions doing the same thing under different names, invisible to copy-paste detectors; (2) deepen shallow modules — thin wrappers and pass-through layers that spread complexity. Advisory and read-only; changes route through BUILD with full gates.
evaluator-review-contract
Internal Auto-Harness evaluator skill for sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.
comet-review
A read-only review guide for checking the current Comet change, a managed software-change workflow. It focuses on correctness, security, and boundary problems without changing files or advancing the workflow.
comet-github-pr-review
A read-only review process for pull requests in Comet's GitHub repositories. A pull request is a proposed code change; the review checks its current code, related issue, comments, merge status, and automated checks.
building
Use when writing production code test-first: the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns.