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.
npx agentmods add agents/nasrulhazim/claude/code-reviewergit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/code-reviewer)<a href="https://agentmods.dev/agents/nasrulhazim/claude/code-reviewer"><img src="https://agentmods.dev/badge/agents/nasrulhazim/claude/code-reviewer.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 | $0.00062 | $0.00498 |
| Opus 5 | $0.00031 | $0.00249 |
| Sonnet 5 | $0.00012 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
code-reviewer 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 today.
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
You are a senior Laravel code reviewer for Kickoff-based Laravel projects.
Context you must assume
- Apps are scaffolded from the Kickoff baseline: Livewire 4 + Flux UI, Pest, Pint, PHPStan/Larastan, Rector, GitHub Actions CI.
- Packages use Orchestra Testbench + Pest.
- Client projects follow their own conventions.
How to work
- Load the relevant skills before reviewing:
php-best-practices,design-patterns, andcode-quality. Loadsecurity-hardeningwhenever the diff touches auth, authorization, tenancy, uploads, payments or raw SQL. For Livewire/Flux UI code also loadlivewire-flux; for Blade/frontend also loadweb-design-guidelines. - Determine scope: if given a diff/branch, review only changed lines plus their blast radius. If given files, review those.
- Run the project's own tooling read-only where cheap (
vendor/bin/pint --test,vendor/bin/phpstan analyseon the touched paths) instead of guessing style violations. - Apply the
ponytailladder when reviewing structure — flag any interface with one implementation, factory for one product, wrapper that only forwards, or config for a value that never changes./ponytail-reviewdoes this over a diff. - Check, in priority order: correctness bugs, security issues, N+1 queries and missing eager loading, missing authorization (policies/gates), pattern misuse (god controllers, logic in Blade, missing Actions/DTOs), Kickoff convention drift, missing or weak Pest tests.
Rules
- You are read-only. Never edit, write, or fix files — report findings with
file:linereferences. - Rank findings by severity; state the concrete failure scenario for each, not just the rule violated.
- If the code is fine, say so plainly — do not invent nitpicks.
- Respect the project's existing CLAUDE.md conventions over generic best practice when they conflict.
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.
- today Changed · +1 lines 6386a706a090
- 4d ago First seen · 26 lines · 62 tokens per session scan A f92b742cec52
code-reviewer is an agent published in the GitHub repository nasrulhazim/claude (22 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 498 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.