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 n24q02m/claude-plugins --skill review-prgit clone --depth 1 https://github.com/n24q02m/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/n24q02m/claude-plugins/review-pr)<a href="https://agentmods.dev/skills/n24q02m/claude-plugins/review-pr"><img src="https://agentmods.dev/badge/skills/n24q02m/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/n24q02m/claude-plugins/review-pr"><img src="https://agentmods.dev/badge/skills/n24q02m/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.00028 | $0.00932 |
| Opus 5.5 | $0.00011 | $0.00373 |
| Sonnet 5.5 | $0.00006 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
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 24d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review PR
Comprehensive code review of a pull request or branch diff against its base. Unlike review-delta (quick review of uncommitted local changes), this reviews ALL commits in a branch for PR submission readiness.
Command surface: run the local CLI through the coding harness shell. Examples
use the installed crg command; from a source checkout,
prefix it with uv run. No MCP mapping is required. Use
crg review --help for the command reference. Never
include full files unless explicitly asked.
Steps
-
Identify the changes for the PR:
- If a PR number or branch is provided, use
git diff main...<branch>to get changed files - Otherwise auto-detect from the current branch vs main/master
- If a PR number or branch is provided, use
-
Update the graph with
crg graph build --base main --repo-root "<path>"so it reflects the current branch. -
Commit-by-commit analysis (for PRs with >3 commits):
git log --oneline main..HEADto list all commits- Group related commits by area (feature, fix, refactor, test, docs)
- Verify each commit message follows Conventional Commits (
type(scope): description) - Flag commits that mix unrelated changes
-
Get the full review context with
crg review context --base main --repo-root "<path>":- Returns all changed files across all commits in the PR
- Includes impacted nodes and blast radius
-
Analyze impact with
crg query impact --base main --repo-root "<path>":- Review the blast radius across the entire PR
- Identify high-risk areas (widely depended-upon code)
-
Breaking change detection for public APIs:
- Identify exported/public functions, classes, types that changed
- Check for: removed parameters, changed return types, renamed exports, removed functions
- Use
crg query query --pattern callers_of --target "<function>" --repo-root "<path>"to find all consumers - Flag any change where callers outside the PR would break
-
Deep-dive each changed file:
- Read the full source of files with significant changes
- Use
crg query query --pattern tests_for --target "<function>" --repo-root "<path>"to verify test coverage - Check for untested new functions
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.
- 24d ago Changed 9f02a566e093
- 2mo ago First seen · 96 lines · 28 tokens per session scan A e965c23a5ae8
review-pr is a skill published in the GitHub repository n24q02m/claude-plugins (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 932 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
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
pr
Analyze changes, detect scope issues, and create a well-structured PR.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
issue-analyzing
Use this skill when the user asks to analyze a specific GitHub issue, understand what area of code an issue affects, assess an issue's scope, or research the code context around an issue — example triggers like "analyze issue.
pr-checklist
Generate a PR checklist based on changes.
babysit
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.