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.
git clone --depth 1 https://github.com/junyoung2015/pr-review-skillWrote 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/commands/junyoung2015/pr-review-skill/pr-review)<a href="https://agentmods.dev/commands/junyoung2015/pr-review-skill/pr-review"><img src="https://agentmods.dev/badge/commands/junyoung2015/pr-review-skill/pr-review.svg" alt="Measured on agentmods" 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.00057 | $0.00308 |
| Opus 5 | $0.00028 | $0.00154 |
| Sonnet 5 | $0.00011 | $0.00062 |
| Haiku 4.5 | $0.00006 | $0.00031 |
Grade A, and why
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 7d 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.
What it actually says
pr-review
Treat the text below as the user's exact PR review request and flags:
$ARGUMENTS
Read and follow the skill at skills/pr-review/SKILL.md.
Interpret $ARGUMENTS exactly as provided by the user. Support these common patterns:
- local PR doc path review
- GitHub PR URL review
--quick--triage-only--auto <PR#>--history <github-id>--review-source <all|coderabbit|copilot|none>--repo-path <abs-path>--review-doc <path>--worktree auto|<abs-path>--dry-run--live
Direct code review is primary. AI review triage is secondary.
For --auto requests:
- run the scripted fetch/worktree preflight before any review or triage work
- never guess the target repo from sibling directories, previous worktrees, or unrelated clones
- if
--repo-pathis absent and the current working directory is not the PR target repo, stop and tell the user to rerun with--repo-path <abs-path>
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.
- 7d ago First seen · 34 lines · 57 tokens per session scan A 9df4def67210
pr-review is a command published in the GitHub repository junyoung2015/pr-review-skill (4 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 308 once invoked, about $0.0003 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-31.
Other commands, from other repositories
genshijin-review
A compact Japanese-language code-review command that reports one finding per line with a severity label and suggested fix.
review-open-prs
Command "review-open-prs" from The-Artificer-of-Ciphers-LLC/skills-from-the-artificer, covering batch pr review directive — all open prs i did not author, phase a — enumerate target prs & build the queue, phase b — per-pr directive (runs once per queued $pr), 0. context anchoring and 1. preconditions.
review
/review [optional: specific files or PR number].
pr-description
Write a pull request description that helps reviewers: what changed, why, and how to verify, from a diff.
review-my-code
Review code for bugs, security issues, and clarity, with severity-ranked findings and concrete fixes.
refactor-code
Suggest refactorings that improve readability and structure without changing behavior, ranked by payoff.