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/muloka/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/muloka/claude-plugins/peer-review-jj)<a href="https://agentmods.dev/plugins/muloka/claude-plugins/peer-review-jj"><img src="https://agentmods.dev/badge/plugins/muloka/claude-plugins/peer-review-jj/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/muloka/claude-plugins/peer-review-jj"><img src="https://agentmods.dev/badge/plugins/muloka/claude-plugins/peer-review-jj.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
peer-review-jj 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 13d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What it installs
The manifest is a name and a version. 2 skills, 1 command, 1 agent travel with it, and installing the plugin installs all of them — 199 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.
- 13d ago Changed 95187b275c0c
- 1mo ago Changed 0a444f4ec8b3
- 1mo ago First seen · 27 lines scan A 1307fedd2536
peer-review-jj is a plugin published in the GitHub repository muloka/claude-plugins (7 stars, last pushed 13d ago), with no licence file. 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
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.
review-pack
Pull-request review pack: /pr-review reviews a GitHub PR and posts verified inline findings, or triages the reviewer comments already on it — verify each against the code, fix the valid ones on the PR branch behind the repo's gates, rebut the rest with file:line evidence, reply in-thread. Opt-in; requires the gh CLI…
review-pr
Review PRs in a Tour Guide (expository) or Adversarial (audit) posture, with logical file ordering, context, and severity-rated findings. Forge-agnostic (GitHub + Bitbucket).
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.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.