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/yankieldbc2/codex-skills-library/deep-code-reviewnpx skills add YankielDBC2/codex-skills-library --skill deep-code-reviewgit clone --depth 1 https://github.com/YankielDBC2/codex-skills-libraryWrote 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/yankieldbc2/codex-skills-library/deep-code-review)<a href="https://agentmods.dev/skills/yankieldbc2/codex-skills-library/deep-code-review"><img src="https://agentmods.dev/badge/skills/yankieldbc2/codex-skills-library/deep-code-review.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00030 | $0.00322 |
| Opus 5 | $0.00015 | $0.00161 |
| Sonnet 5 | $0.00006 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
deep-code-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 4d 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.
What it actually says
Deep Code Review
Goal
Find meaningful issues before merge while avoiding noisy or subjective feedback.
When to use
Use for PR reviews, diffs, architecture reviews, risk reviews, and pre-merge checks.
When not to use
Do not use when the user asks for direct implementation rather than review.
Inputs
Inspect the diff, changed files, tests, affected public interfaces, dependency changes, and related docs.
Workflow
- Understand the intent of the change.
- Review correctness first.
- Check edge cases, error handling, data validation, and auth boundaries.
- Check security and privacy risks.
- Check maintainability, duplication, and architecture fit.
- Check tests and validation coverage.
- Prioritize findings by impact.
- Avoid comments that are only personal style preferences.
Severity levels
- Blocker: likely production breakage, data loss, security issue, or failed build.
- Major: likely bug, missing validation, risky architecture, or poor test coverage.
- Minor: maintainability or clarity issue worth fixing.
- Nit: optional style improvement.
Validation
Recommend or run relevant tests, lint, typecheck, build, and security checks.
Final response
List findings by severity with file references when possible. Include positives only if helpful and brief.
What ships with it
4 files 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.
- 4d ago First seen · 52 lines · 30 tokens per session scan A 61802e6e745e
deep-code-review is a skill published in the GitHub repository YankielDBC2/codex-skills-library (10 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 322 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-31.
Other skills, from other repositories
design-critique
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
local-clawsweeper-review
Run local ClawSweeper exact-item or committed-range reviews without GitHub mutation.
ralphex-adopt
Convert plans from various source formats (OpenSpec, spec-kit, GitHub/GitLab issues with checklists, generic task-lists, free-form markdown) into ralphex-format plans in docs/plans/. Triggers on "ralphex-adopt", "adopt plan", "convert plan to ralphex", "import plan as ralphex".
ralphex
Run ralphex autonomous plan execution with progress monitoring.