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/duyet/oma/code-reviewnpx skills add duyet/oma --skill code-reviewgit clone --depth 1 https://github.com/duyet/omaWhat 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.00085 | $0.01063 |
| Opus 5 | $0.00043 | $0.00531 |
| Sonnet 5 | $0.00017 | $0.00213 |
| Haiku 4.5 | $0.00009 | $0.00106 |
Grade A, and why
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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-review
A review answers one question: is this change correct, safe, and something the team can live with? Read before you judge — a diff in isolation lies. The bug is usually in what the diff doesn't show: the caller that still passes the old shape, the error path that's now unreachable, the invariant two files over.
Scope the review first
- Get the diff.
git diff main...HEAD(or the branch/commit the user named). For an uncommitted change,git diff/git diff --staged. - Read what it touches. For every changed function, read its callers and
the code it calls.
grepthe symbol across the repo. "Looks orthogonal" is how regressions ship. - Know the intent. What was this supposed to do — the issue, the PR body, the commit message? A change can be flawless code and still be the wrong change. Review against the goal, not just against the compiler.
What to look for, in priority order
Spend your attention where the damage is greatest.
- Correctness — Does it do what it claims? Off-by-one, inverted
conditions, wrong operator, missing
await, unhandlednull/undefined, the empty-list and single-element cases, integer overflow, timezone/Datemistakes. Trace one real input through the new path by hand. - Security — Untrusted input reaching a sink: SQL/command/template injection, path traversal, SSRF, deserialization. Missing authz on a new route. Secrets in code, logs, or errors. A dependency bump to an unvetted version. See the checklist below.
- Error handling — Failures that are swallowed, logged-and-ignored, or caught too broadly. Resources (connections, files, locks, timers) leaked on the error path. Partial writes that leave state inconsistent.
- Concurrency & data — Races, unawaited promises, shared mutable state, N+1 queries, unbounded loops/allocations on user-controlled size, missing pagination, a migration that locks a hot table.
- Tests — Is the new behavior actually tested? A test that can't fail when the logic breaks is theater. Check the edge cases the code added, not just the happy path.
- Maintainability — Naming that misleads, a 200-line function that should be 50, duplicated logic, a leaked abstraction, dead code the change orphaned. Real, but never rank it above a correctness or security finding.
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 · 82 lines · 85 tokens per session scan A 36d200cda85b
code-review is a skill published in the GitHub repository duyet/oma (5 stars, last pushed 13d ago), licensed Apache-2.0. It adds 85 tokens to every session and 1,063 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…