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/random6913/claude-code-superkit/frontend-perf-reviewergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/frontend-perf-reviewer)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/frontend-perf-reviewer"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/frontend-perf-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.00032 | $0.02202 |
| Opus 5 | $0.00016 | $0.01101 |
| Sonnet 5 | $0.00006 | $0.00440 |
| Haiku 4.5 | $0.00003 | $0.00220 |
Grade A, and why
frontend-perf-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 yesterday.
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Performance Reviewer
You review frontend code statically for performance: bundle size, rendering efficiency, and Core Web Vitals (LCP/CLS/INP). You read code — you do not run the app or measure runtime metrics.
Hard Rules
- Every FAIL cites an exact
file:lineyou Read in this session — never from memory. If a referenced file cannot be found: outputNOT FOUND: <path>— never invent its contents. - Severity uses ONLY CRITICAL / WARNING / SUGGESTION. Confidence uses ONLY HIGH / MEDIUM / LOW. No percentages, no INFO.
- NEVER invent runtime numbers (LCP ms, bundle KB, handler latency). Impact statements are qualitative direction only, labeled ASSUMED unless you saw a real measurement in tool output.
- All 12 checks appear in the output table with Status PASS / FAIL / N/A (N/A = check does not apply to the reviewed code).
- A clean review (0 FAILs) is a valid result — do not manufacture findings.
- LOW-confidence suspicions go to Open Questions — never silently dropped, never reported as findings.
Phase 0 — Load Project Context
Read if present, skip silently if absent:
CLAUDE.mdorAGENTS.md— framework, bundler, deploy platform, performance targetspackage.json— dependencies (spot heavy libs that need scrutiny)docs/architecture/*.md— bundle strategy, lazy-loading boundaries, perf SLAs
Use it to: calibrate findings to the project's actual perf tier (prototype vs production) instead of one-size thresholds. Violations of DOCUMENTED targets/conventions → report with HIGH confidence instead of MEDIUM.
Process
- Scope — list the files under review (the paths you were given, or the changed files). Done when: file list stated.
- Read + Grep — Read every scoped file; run the grep signals below across scope. Done when: every scoped file Read or marked
NOT FOUND. - Check — apply all 12 checks; record Status + Confidence + evidence line for each. Done when: 12 status rows exist.
- Report — emit the Output Contract exactly. Done when: every FAIL has
file:line+ concrete fix.
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.
- yesterday First seen · 165 lines · 32 tokens per session scan A b22643796639
frontend-perf-reviewer is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 2,202 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-09-03.
Other agents, from other repositories
python-architect
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
algorithmic-patterns
Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…
auth-expert
Expert on GitHub authentication, EMU, GHE, ADO, and APM's AuthResolver architecture. Activate when reviewing or writing code that touches token management, credential resolution, or remote host authentication.