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/dcosson/h2/code-reviewnpx skills add dcosson/h2 --skill code-reviewgit clone --depth 1 https://github.com/dcosson/h2What 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.00033 | $0.01565 |
| Opus 5 | $0.00016 | $0.00783 |
| Sonnet 5 | $0.00007 | $0.00313 |
| Haiku 4.5 | $0.00003 | $0.00156 |
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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Review the implementation for a bead or feature. Produce a structured review doc with severity-rated findings — the same disposition-table pattern used for plan reviews, applied to code.
Inputs
$0: Bead ID (e.g.,edb-d6kq.3) or commit range (e.g.,abc123..def456)$1: Reviewer identifier (e.g.,reviewer-1, used in output filename)- Review docs directory:
docs/reviews/(created if it doesn't exist)
Critical Rules
- Do NOT review code you wrote. Fresh eyes catch more issues.
- Do NOT read other reviewers' review files for the same bead before completing your own review. Reviews must be independent.
- Review the actual code diff, not just the plan. The plan says what should be built — the review verifies what was built.
- For beads that include external/E2E/acceptance tests: the reviewer MUST execute the tests against a running system, not just review the test code. Tests that compile but were never run against the actual system are not reviewed. If the reviewer cannot run the tests (e.g., missing infrastructure), they must flag this as a blocker rather than approving.
Phase 1: Scope the Review
If given a bead ID:
- Look up the bead:
bd show $0 - Find the associated commits:
git log --all --grep="Bead: $0"and any commits on branches named after the bead - Find the plan doc referenced by the bead or its parent epic
- Identify the commit range to review
If given a commit range:
- Use the range directly
- Check commit messages for
Plan-Ref:orBead:trailers to find the associated plan doc
Gather context:
- Read the plan doc (if found) to understand intent
- Run
git diff <range>to see the full code diff - Read the changed files in full (not just the diff) to understand surrounding context
- Read any test changes to understand test coverage
Phase 2: Analyze
Evaluate the implementation for:
Correctness
- Does the code match what the plan specifies?
- Race conditions, deadlocks, or unsafe concurrent access
- Off-by-one errors, nil/zero-value handling, error swallowing
- Resource leaks (unclosed handles, goroutine leaks, missing defers)
- Crash recovery and restart safety
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 · 171 lines · 33 tokens per session scan A e55bbe435c94
code-review is a skill published in the GitHub repository dcosson/h2 (159 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 1,565 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.
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…