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 dcosson/h2 --skill code-review-incorporategit clone --depth 1 https://github.com/dcosson/h2Wrote 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/dcosson/h2/code-review-incorporate)<a href="https://agentmods.dev/skills/dcosson/h2/code-review-incorporate"><img src="https://agentmods.dev/badge/skills/dcosson/h2/code-review-incorporate.svg" alt="Measured on agentmods" 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.00042 | $0.01758 |
| Opus 5 | $0.00021 | $0.00879 |
| Sonnet 5 | $0.00008 | $0.00352 |
| Haiku 4.5 | $0.00004 | $0.00176 |
Grade A, and why
code-review-incorporate 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 8d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Incorporate
Incorporate findings from a code review doc into the implementation. Make the code changes, commit with structured trailers linking back to the review, and update the review doc's disposition table.
Inputs
$0: Path to the review doc (e.g.,docs/reviews/edb-d6kq.3-r1-review-reviewer-1.md)
Phase 1: Read & Understand
- Read the review doc at
$0 - Extract: bead ID, commit range reviewed, plan doc path, reviewer name, findings list
- Read the plan doc (if referenced) to understand original intent
- Read the code files referenced in each finding
- Check for existing disposition tables in the review doc (from prior incorporate rounds on the same review)
Phase 2: Evaluate Each Finding
For every finding in the review doc:
- Read the referenced code and understand the issue
- Decide disposition:
- Incorporate: The finding is valid — plan the code fix
- Not Incorporate: The finding is invalid or the current code is intentional — prepare rationale
- Deferred: Valid but out of scope — create a follow-up bead
Disposition Criteria
Valid reasons for "Not Incorporate":
- The current code is intentional and the reviewer misunderstands the design
- The change would introduce import cycles or architectural violations
- The finding conflicts with a decision documented in the plan doc
- The reviewer's suggested fix has correctness issues of its own
Invalid reasons for "Not Incorporate":
- "Too much work" (effort is not a factor)
- "Works fine as-is" (if there's a real quality issue, fix it)
Phase 3: Discussion with Reviewer
Do not apply changes yet. Reach consensus with the reviewer first.
Step 1: Send Proposed Dispositions
Send a single h2 send message to the reviewer with proposed dispositions:
Proposed dispositions for {review-doc-path}:
1. P0 - {title}: Incorporate — {brief description of planned fix}
2. P1 - {title}: Not Incorporate — {rationale}
3. P2 - {title}: Incorporate — {brief description}
...
Please confirm, or push back on any you disagree with.
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.
- 8d ago First seen · 182 lines · 42 tokens per session scan A e85f7ff4f648
code-review-incorporate is a skill published in the GitHub repository dcosson/h2 (159 stars, last pushed 12d ago), licensed MIT. It adds 42 tokens to every session and 1,758 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
pr-pending-feedback
Evaluate pending (unsubmitted) review comments on the current branch's PR and, after user confirmation, address each in a separate sub-agent and separate commit.