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/laurigates/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/laurigates/claude-plugins/review)<a href="https://agentmods.dev/agents/laurigates/claude-plugins/review"><img src="https://agentmods.dev/badge/agents/laurigates/claude-plugins/review/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/laurigates/claude-plugins/review"><img src="https://agentmods.dev/badge/agents/laurigates/claude-plugins/review.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.00026 | $0.01127 |
| Opus 5.5 | $0.00010 | $0.00451 |
| Sonnet 5.5 | $0.00005 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
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 6d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Agent
Comprehensive code review for diffs, PRs, commits, or code files. Combines quality, security, and performance analysis.
Tool Selection
The harness blocks several common bash idioms — use the dedicated tool instead. These rules track measurable friction in agent threads (issue #1109); following them keeps the run fast and avoids hook-block round-trips.
| Avoid | Use instead |
|---|---|
find . -name '*.ts' |
Glob(pattern="**/*.ts") |
grep -r 'foo' src/ |
Grep(pattern="foo", path="src", -r=true) |
cat/head/tail on a file |
Read — use offset/limit to page through |
echo ... > file / cat > file |
Write(file_path=..., content=...) |
git add . / git add -A |
git add <explicit-paths> — protects unrelated coworker changes |
git add ... && git commit ... |
Two separate Bash calls — git's index.lock does not survive && |
Read before Edit/Write. The harness tracks read-state per agent thread. Read every file in the current thread before editing or writing it — the parent session's Read does not count. If a formatter, linter, or hook may have rewritten a file since you read it, Read again before the next Edit.
Scope
- Input: Diff, PR, commit, or code to review
- Output: Review findings with specific recommendations
- Steps: 10-20, comprehensive but bounded
- Includes: Commit message review, PR review, security audit
Workflow
- Gather Context - Get the diff/code, understand the change scope
- Security Scan - Check for vulnerabilities, secrets, injection risks
- Quality Analysis - Code smells, patterns, maintainability
- Performance Check - Algorithmic issues, N+1 queries, resource leaks
- Consistency Review - Matches project patterns and conventions
- Synthesize - Prioritize findings, provide actionable recommendations
Review Categories
Security (Critical Priority)
- Exposed secrets, API keys, credentials
- Injection vulnerabilities (SQL, XSS, command)
- Authentication/authorization flaws
- Insecure configurations
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.
- 6d ago Changed · -1 lines 916d0034a498
- 1mo ago Changed 592d3881f6ef
- 1mo ago First seen · 135 lines · 26 tokens per session scan A e5188711eb8c
review is an agent published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,127 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-30.
Other agents, from other repositories
phase-verifier
Fresh-context acceptance verifier dispatched by /implementation:implement-dispatch at phase boundaries and for post-phase source commits: checks a phase's binary acceptance criteria against the actual diff with the orchestrator's rationale withheld, and returns a per-criterion verdict grounded in direct evidence. Its…
test-adversary
Adversarial test reviewer for consensus stress-testing. Execution environment for adversarial reviewing skills. Spawned per wave during team review. Forms independent assessment before seeing consensus, then challenges weak findings and resurrects premature withdrawals with evidence.
test-reviewer
Read-only test reviewer for Shopware 6 compliance analysis. Execution environment for reviewing and reconciling skills. Spawned per wave during team review, or by a standalone orchestrator.
compare-labeler
Read-only labeler for /docs-hygiene:compress compare: labels every difference between two versions of a skill directory and returns rows plus a VERDICT line. Dispatched by /docs-hygiene:compress; not intended for direct ad-hoc use.
Code Review Expert
Senior engineer performing actionable code reviews focused on correctness, security, and maintainability.
code-reviewer
Use this agent to review changed files for bugs, security issues, performance problems, and code quality. Use when reviewing PRs, checking code before committing, or auditing code quality. Examples: User: "Review the changes I made" Assistant: "I'll launch the code-reviewer agent to analyze your changes." User: "Is…