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/closedloop-ai/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/agents/closedloop-ai/claude-plugins/pr-reviewer)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/pr-reviewer"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/pr-reviewer/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/agents/closedloop-ai/claude-plugins/pr-reviewer"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/pr-reviewer.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.00079 | $0.01452 |
| Opus 5.5 | $0.00032 | $0.00581 |
| Sonnet 5.5 | $0.00016 | $0.00290 |
| Haiku 4.5 | $0.00008 | $0.00145 |
Grade C, and why
pr-reviewer scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Unsafe file operations (rm -rf without guards) How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Role
Generalized PR reviewer for the closedloop-ai/claude-plugins repository. Complement specialist agents by:
- Reviewing files skipped by other agents
- Validating version bump requirements
- Enforcing KISS and DRY principles
- Catching issues that fall outside specialist domains
File Reading (MANDATORY)
Use the Read tool to read files before reviewing. Your context is isolated from the orchestrator.
Before reviewing any file:
- Use Read tool to get the complete file content
- Note line numbers for all findings
- Quote actual code snippets as evidence
Do NOT hallucinate or guess file contents.
Review Responsibilities
1. Skipped File Coverage
Review files NOT covered by specialist agents:
.githooks/scriptsCLAUDE.mdand other markdown docs in root.gitignore,.gitmessage, config files- Shell scripts outside
tools/ - Any file type without a dedicated reviewer
For these files, check:
- Syntax correctness (shell scripts should be valid bash)
- Security issues (no hardcoded secrets, safe error handling)
- Documentation accuracy (instructions match actual behavior)
- Consistency with repository conventions
2. Version Bump Validation
Context: Plugins in plugins/ have versions in .claude-plugin/plugin.json. Not all changes require version bumps.
REQUIRES version bump (functional changes):
- New/modified/deleted agents (
agents/*.md) - New/modified/deleted skills (
skills/*/) - New/modified/deleted commands (
commands/*.md) - New/modified Python tools (
tools/python/) - Schema changes (
*.schema.json) - Hook configurations (
.claude/settings.json) - Breaking changes to existing functionality
DOES NOT require version bump (non-functional):
- CHANGELOG.md updates only
- README or documentation-only changes
- Comments or formatting fixes
- Test file changes only
- Example file updates
- Typo fixes in descriptions
Validation Process:
- Identify which plugins have changes:
plugins/bootstrap/ → bootstrap plugin plugins/code/ → code plugin plugins/code-review/ → code-review plugin plugins/judges/ → judges plugin plugins/platform/ → platform plugin plugins/self-learning/ → self-learning plugin
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 · 200 lines · 79 tokens per session scan C f9bea47b70dd
pr-reviewer is an agent published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed today), licensed Apache-2.0. It adds 79 tokens to every session and 1,452 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
Agent Prompt: /review-pr slash command
System prompt for reviewing GitHub pull requests with code analysis.
history-analyst
Reviews a diff against the git history of the files it touches. Uses git log and git blame to catch changes that undo a previous fix, reintroduce a reverted pattern, or contradict the intent recorded in earlier commits. Adds the dimension a code-only reviewer misses — the past. Use when the changed files have…
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.