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 cblecker/claude-plugins --skill review-prgit clone --depth 1 https://github.com/cblecker/claude-pluginsWrote 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/cblecker/claude-plugins/review-pr)<a href="https://agentmods.dev/skills/cblecker/claude-plugins/review-pr"><img src="https://agentmods.dev/badge/skills/cblecker/claude-plugins/review-pr/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/cblecker/claude-plugins/review-pr"><img src="https://agentmods.dev/badge/skills/cblecker/claude-plugins/review-pr.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.00018 | $0.01802 |
| Opus 5.5 | $0.00007 | $0.00721 |
| Sonnet 5.5 | $0.00004 | $0.00360 |
| Haiku 4.5 | $0.00002 | $0.00180 |
Grade A, and why
review-pr 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 20d 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.
PR Review
Precondition
This skill takes no arguments. The current directory must be a git checkout
of the PR head commit — a Claude Code worktree (claude --worktree "#123"),
gh pr checkout N, or the author's own up-to-date branch.
Environment
- Head SHA: !
git rev-parse HEAD - Checkout root: !
git rev-parse --show-toplevel - Branch: !
git rev-parse --abbrev-ref HEAD - Origin: !
git remote get-url origin | cut -d@ -f2- - Branch config: !
git config --get-regexp '^branch\..*\.merge$' - Dirty files: !
git status --porcelain
Constraints
Use only allowed-tools. Do not generate ad-hoc processing scripts. Workflow
return values and MCP responses are structured JSON; read them directly. Bash
is limited to the read-only git commands used below plus one git fetch of
the base branch. The workflow and its agents are read-only. GitHub write
tools may be used only after an exact preview and explicit final posting
approval from the user.
Exit Plan Mode
If plan mode is active, call ExitPlanMode now before proceeding.
Resolve The PR
Determine which PR this checkout belongs to, from the Environment values
above. Origin's host must be github.com; parse {owner}/{repo} from it. The
next section verifies the candidate's head SHA, so resolution only has to
produce the right candidate, not prove it. In the same turn as the first
GitHub call, also call get_me (see Identify The Reviewer) and Read
${CLAUDE_SKILL_DIR}/references/board.md; neither depends on the PR. Use the
first route that yields one:
- Branch config — if the current branch's
mergekey in Branch config isrefs/pull/N/head(asgh pr checkoutwrites for fork checkouts), N is the PR number. - Head filter — on a named branch, call
list_pull_requestswith stateopen, head{owner}:{branch}(an exact server-side filter), andfields: ["number", "head"]. - SHA scan — otherwise: scan
list_pull_requestswith stateopen,perPage: 100, andfields: ["number", "head"]to the last page forhead.shaequal to the Head SHA.search_pull_requestswith queryrepo:{owner}/{repo} is:pr is:open {headSha}may suggest a candidate first, but it is only a hint: its index lags recent pushes and matches PRs that merely mention the SHA.
What ships with it
3 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.
- 20d ago Changed · +10 lines dbe1a51c9f4d
- 22d ago Changed · -85 lines 5c5930f5ba90
- 28d ago Changed · +4 lines 6d527c50f53b
- 1mo ago Changed · +7 lines e4a5a3a7a397
- 1mo ago First seen · 235 lines · 18 tokens per session scan A 07e46ac351c8
review-pr is a skill published in the GitHub repository cblecker/claude-plugins (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,802 once invoked, about $0.0001 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
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.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…