Borrowing it
Nothing to install: this file belongs to theagenticguy/opencodehub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/theagenticguy/opencodehub/main/.claude/skills/opencodehub-pr-review/SKILL.mdgit clone --depth 1 https://github.com/theagenticguy/opencodehubWrote 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/theagenticguy/opencodehub/opencodehub-pr-review)<a href="https://agentmods.dev/skills/theagenticguy/opencodehub/opencodehub-pr-review"><img src="https://agentmods.dev/badge/skills/theagenticguy/opencodehub/opencodehub-pr-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/theagenticguy/opencodehub/opencodehub-pr-review"><img src="https://agentmods.dev/badge/skills/theagenticguy/opencodehub/opencodehub-pr-review.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00065 | $0.02572 |
| Opus 5.5 | $0.00026 | $0.01029 |
| Sonnet 5.5 | $0.00013 | $0.00514 |
| Haiku 4.5 | $0.00006 | $0.00257 |
Grade A, and why
opencodehub-pr-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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- codehub-pr-review — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review with OpenCodeHub
When to Use
- "Review this PR."
- "What does PR #42 change?"
- "Is this safe to merge?"
- "What's the blast radius of this PR?"
- "Are there missing tests for this PR?"
- "Did this PR introduce a copyleft / unknown license?"
- Reviewing someone else's code changes before merge.
The Golden Workflow
1. mcp__codehub__verdict({ base, head }) → 5-tier merge decision
2. mcp__codehub__list_findings_delta({ base }) → New / fixed / unchanged / updated findings
3. mcp__codehub__detect_changes({ scope: "compare", base_ref }) → Changed symbols + affected flows
4. For each non-trivial changed symbol:
mcp__codehub__impact({ name, direction: "upstream" }) → Blast radius + confidenceBreakdown
5. mcp__codehub__license_audit → Copyleft / unknown / proprietary tiers
6. mcp__codehub__scan (opt-in) → Fresh scanner run — spawns processes
7. Write the review using the output template below
If the context envelope warns the index is stale, run
codehub analyzebefore starting — stale graphs produce stale verdicts.
Checklist
- [ ] Fetch the PR diff (gh pr diff <n> or git diff <base>...<head>)
- [ ] mcp__codehub__verdict — start here; it aggregates the review signal
- [ ] Capture the verdict tier, top drivers, and blockers
- [ ] mcp__codehub__list_findings_delta — new findings since the baseline
- [ ] mcp__codehub__detect_changes — map the diff to affected processes
- [ ] mcp__codehub__impact on each non-trivial changed symbol
- [ ] Inspect confidenceBreakdown per impact — prefer confirmed edges for breakage claims
- [ ] mcp__codehub__license_audit — flag copyleft or unknown license changes
- [ ] (optional) mcp__codehub__scan to re-run scanners if the baseline is stale
- [ ] Write the review in the output template below
Tools
mcp__codehub__verdict — the starting point
mcp__codehub__verdict({ base: "main", head: "HEAD", repo: "my-app" })
→ tier: "auto_merge" | "single_review" | "dual_review" | "expert_review" | "block"
→ drivers: [{ signal, weight, evidence }] // top reasons the tier was chosen
→ blockers: [...] // non-empty only for tier=block
→ next_action: "merge" | "request review from X" | "add tests for Y" | "fix finding Z"
→ exit_code: 0 | 1 | 2
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.
- 2mo ago First seen · 247 lines · 65 tokens per session scan A 00b6c8c30ede
opencodehub-pr-review is a skill published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 65 tokens to every session and 2,572 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-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…