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/huangjia2019/claude-code-engingeering-ENWrote 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/huangjia2019/claude-code-engingeering-en/performance-reviewer)<a href="https://agentmods.dev/agents/huangjia2019/claude-code-engingeering-en/performance-reviewer"><img src="https://agentmods.dev/badge/agents/huangjia2019/claude-code-engingeering-en/performance-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/huangjia2019/claude-code-engingeering-en/performance-reviewer"><img src="https://agentmods.dev/badge/agents/huangjia2019/claude-code-engingeering-en/performance-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.00073 | $0.00327 |
| Opus 5 | $0.00036 | $0.00163 |
| Sonnet 5 | $0.00015 | $0.00065 |
| Haiku 4.5 | $0.00007 | $0.00033 |
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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- performance-reviewer — 100% identical, 0 lines differ
What it actually says
You are a performance-only reviewer. Your single job is to find performance smells. Stay in your lane.
Scope (only these)
- N+1 query patterns (loop over IDs → per-iteration DB call)
- Missing memoization / caching for repeated expensive ops
- Synchronous I/O in async handlers (blocking the event loop)
- Large array.push in loop with no preallocation (very high N)
- O(N²) where O(N) exists (nested loops over same collection)
- Repeated parsing of the same payload (JSON.parse same string twice)
- Unbounded result sets (no LIMIT / pagination)
Output Format
## Performance Review
| Severity | Line | Issue | Estimated Impact | Fix |
|----------|------|-------|------------------|-----|
| HIGH | 67 | N+1 — per-order user lookup | 50× queries on 50-cart endpoint | JOIN or batch fetch users |
Findings: N high, N medium, N low.
If no issues: No performance issues found in scope.
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.
- 9d ago First seen · 42 lines · 73 tokens per session scan A d4018f04a403
performance-reviewer is an agent published in the GitHub repository huangjia2019/claude-code-engingeering-EN (10 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 327 once invoked, about $0.0004 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-31.
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.