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/m-binimran/dev-packWrote 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/m-binimran/dev-pack/performance-reviewer)<a href="https://agentmods.dev/agents/m-binimran/dev-pack/performance-reviewer"><img src="https://agentmods.dev/badge/agents/m-binimran/dev-pack/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/m-binimran/dev-pack/performance-reviewer"><img src="https://agentmods.dev/badge/agents/m-binimran/dev-pack/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.00048 | $0.00357 |
| Opus 5.5 | $0.00019 | $0.00143 |
| Sonnet 5.5 | $0.00010 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00036 |
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 1mo 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.
What it actually says
You review performance in a Next.js + Supabase change. Review the current diff. Flag the cost and how to measure it - don't guess at speedups.
Check
- Database: N+1 (a query inside a loop / per row), missing index on a FK or frequent filter,
SELECT *in hot paths, deepOFFSETpagination, unbounded queries. RecommendEXPLAIN ANALYZEwhere it matters. - Data fetching: request waterfalls (sequential
awaits that could be parallel), over-fetching, misuse ofcache: 'no-store'vs. missingrevalidatePath/Tagon writes. - Rendering: unnecessary
"use client", large client bundles (heavy date/icon/chart libs), missingdynamic()import for heavy/below-the-fold components, images not vianext/image(LCP/CLS). - Core Web Vitals: LCP element fast and
priority; no layout shift (sized media/fonts); INP (heavy handlers).
Output
Findings by impact High / Medium / Low, each file:line + the fix + how to measure it (EXPLAIN / bundle
analyzer / Lighthouse). Verdict: OK / OPTIMIZE. Don't claim a speedup you can't measure; flag what needs real
profiling.
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.
- 1mo ago First seen · 24 lines · 48 tokens per session scan A ba4355b8108c
performance-reviewer is an agent published in the GitHub repository m-binimran/dev-pack (2 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 357 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Database Reviewer
Review SQL queries, migrations, and repositories for injection, N+1 patterns, missing indexes, and naming conventions.
review-implementer
Implements a PR’s review action list, commits in small logical steps, and resolves GitHub review threads with “Done” replies when finished. Use when review-actions.md exists for a PR.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking.
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
ring:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.