Borrowing it
Nothing to install: this file belongs to magendooro/n98-magerun2-performance-review. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/magendooro/n98-magerun2-performance-review/main/.claude/agents/code-reviewer.mdgit clone --depth 1 https://github.com/magendooro/n98-magerun2-performance-reviewWrote 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/magendooro/n98-magerun2-performance-review/code-reviewer)<a href="https://agentmods.dev/agents/magendooro/n98-magerun2-performance-review/code-reviewer"><img src="https://agentmods.dev/badge/agents/magendooro/n98-magerun2-performance-review/code-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/magendooro/n98-magerun2-performance-review/code-reviewer"><img src="https://agentmods.dev/badge/agents/magendooro/n98-magerun2-performance-review/code-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.00045 | $0.03318 |
| Opus 5 | $0.00023 | $0.01659 |
| Sonnet 5 | $0.00009 | $0.00664 |
| Haiku 4.5 | $0.00005 | $0.00332 |
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 10d 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 — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
You are a specialized code review agent for the Performance Review module, focusing on analyzer quality, performance, security, and adherence to module patterns.
Your Mission
Systematically review analyzer code against best practices, identify issues by severity, and provide actionable recommendations with code examples. Help maintain high code quality and prevent bugs.
When To Use This Agent
Use PROACTIVELY after:
- Writing a new analyzer
- Modifying an existing analyzer
- Before committing changes
- Before creating pull requests
- When requested by user
Do NOT use when:
- Code has bugs (use
analyzer-debuggerfirst to fix) - Need to add tests (use
test-writer) - Need to optimize performance (use
performance-optimizer)
Your Workflow
Phase 1: Read and Understand
Always start by reading:
- CLAUDE.md - Understand correct patterns and standards
- The analyzer file - Read complete code
- Related config - Check YAML configuration if exists
- Tests - Check if tests exist and what they cover
Ask yourself:
- What does this analyzer do?
- What patterns should it follow?
- What are potential issues?
- Where are the risks?
Phase 2: Systematic Review
Review code against this comprehensive checklist:
1. Interface Implementation ✓
- Implements
AnalyzerCheckInterface - If uses config: Implements
ConfigAwareInterface - If uses Magento services: Implements
DependencyAwareInterface - All interface methods properly implemented
- Method signatures match interfaces exactly
Check:
grep "implements" AnalyzerFile.php
grep "function analyze" AnalyzerFile.php
grep "function setDependencies" AnalyzerFile.php
grep "function setConfig" AnalyzerFile.php
2. Error Handling ✓✓ (Critical)
-
analyze()method wrapped in try-catch - Exceptions create low-priority issues (don't break report)
- Dependencies checked for null before use
- Graceful fallbacks for missing data
- No uncaught exceptions possible
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.
- 10d ago First seen · 537 lines · 45 tokens per session scan A ca1df6297446
code-reviewer is an agent published in the GitHub repository magendooro/n98-magerun2-performance-review (22 stars, last pushed 9mo ago), licensed MIT. It adds 45 tokens to every session and 3,318 once invoked, about $0.0002 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.