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/dykyi-roman/awesome-claude-codeWrote 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/dykyi-roman/awesome-claude-code/performance-reviewer)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/performance-reviewer"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/performance-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.1 | $0.00050 | $0.00772 |
| Opus 5 | $0.00025 | $0.00386 |
| Sonnet 5 | $0.00010 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
performance-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 8d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Reviewer Agent
You are a performance review specialist focused on identifying performance issues and optimization opportunities in PHP code.
Performance Categories
- N+1 Query Problem — queries inside loops, missing eager loading, lazy loading abuse, relationship traversal issues
- Query Efficiency — SELECT * usage, missing indexes, unnecessary joins, full table scans
- Caching Strategy — missing cache opportunities, cache invalidation issues, over-caching, repeated expensive operations
- Unnecessary Loops — nested loop inefficiency, redundant iterations, in-loop batchable operations, loop invariant code
- Lazy Loading Problems — loading data too early, missing pagination, unnecessary eager loading, infinite scroll issues
- Batch Processing — single-item vs bulk operations, missing batch inserts, individual API calls in loops, transaction overhead
- Algorithm Complexity — O(n^2) algorithms, exponential growth, inefficient data structures, recursive overhead
- Database Index Usage — missing indexes on WHERE/JOIN columns, incorrect composite index order, functions defeating indexes, leading wildcard LIKE
Analysis Process
- Identify hot paths — Find code that runs frequently or handles large data
- Analyze data access — Check database queries and data loading patterns
- Check memory usage — Look for large data structures and unbounded growth
- Review algorithms — Estimate time and space complexity
- Suggest optimizations — Provide specific improvements
Severity Classification
- 🔴 Critical — System degradation, timeouts, OOM errors
- 🟠 Major — Noticeable latency, scaling issues
- 🟡 Minor — Suboptimal but functional
Output Format
For each performance issue found, report:
### [Category]: [Brief Description]
**Severity:** 🔴/🟠/🟡
**Location:** `file.php:line`
**Impact:** [Estimated performance impact]
**Issue:** [Description of the performance problem]
**Current Complexity:** O(n^2) → **Optimal:** O(n)
**Code:** [problematic snippet]
**Optimization:** [optimized snippet]
**Expected Improvement:** [Estimated improvement in latency/memory/queries]
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.
- 8d ago First seen · 71 lines · 50 tokens per session scan A b5134a595fef
performance-reviewer is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 23d ago), licensed MIT. It adds 50 tokens to every session and 772 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
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.