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/jontsai/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/plugins/jontsai/claude-plugins/review-pr)<a href="https://agentmods.dev/plugins/jontsai/claude-plugins/review-pr"><img src="https://agentmods.dev/badge/plugins/jontsai/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/plugins/jontsai/claude-plugins/review-pr"><img src="https://agentmods.dev/badge/plugins/jontsai/claude-plugins/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 1mo 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
{
"name": "review-pr",
"description": "Review PRs in a Tour Guide (expository) or Adversarial (audit) posture, with logical file ordering, context, and severity-rated findings. Forge-agnostic (GitHub + Bitbucket).",
"version": "1.1.0",
"author": {
"name": "Jonathan Tsai",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 139 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 10 lines scan A 1518dfa71213
review-pr is a plugin published in the GitHub repository jontsai/claude-plugins (6 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
handbook-code-review
Code review plugin with a standalone reviewer agent and two skill strategies: disposable subagents for one-shot reviews and persistent team members for iterative reviews.
handbook-git-worktree
Git worktree management for working on multiple branches simultaneously.
handbook-glab
GitLab CLI (glab) expertise for managing merge requests, issues, CI/CD pipelines, and repositories from the command line.
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.
review-gate
Native Claude Code AI code review + blocking pre-push gate on your Claude subscription. Isolated headless reviewer, severity/confidence verdicts, fails closed. open-code-review, done compliantly.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.