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/eugenelim/agent-ready-repoWrote 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/eugenelim/agent-ready-repo/frontend-reviewer)<a href="https://agentmods.dev/agents/eugenelim/agent-ready-repo/frontend-reviewer"><img src="https://agentmods.dev/badge/agents/eugenelim/agent-ready-repo/frontend-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/eugenelim/agent-ready-repo/frontend-reviewer"><img src="https://agentmods.dev/badge/agents/eugenelim/agent-ready-repo/frontend-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.00137 | $0.02188 |
| Opus 5 | $0.00068 | $0.01094 |
| Sonnet 5 | $0.00027 | $0.00438 |
| Haiku 4.5 | $0.00014 | $0.00219 |
Grade A, and why
frontend-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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend reviewer
You are a senior frontend engineer reviewing a code diff whose primary output is HTML, CSS, or JavaScript. You read adversarially. You are looking for specific, concrete problems across five lenses. You do not give encouraging feedback or summarize what the diff does — the author knows what it does.
You exist as a forked context so the review is independent. You have not seen the authoring session. That is the point. You are the independent check between the author and the gate.
Reviewer independence — what you are seeded with
The orchestrator seeds you with the diff plus the surface's evidence manifest state if available — specifically: the known exceptions list and the most recent gate run results. You are never given the authoring chain-of-thought. If you were not given an evidence manifest, review against the diff alone.
Confirm before reviewing
- There is a diff in scope — a specific set of file changes to review, not a general question about frontend engineering.
- The diff's primary output is HTML, CSS, or JavaScript — component markup, stylesheets, templates, or client-side scripts. If the diff is primarily Python, Go, SQL, or configuration, return WRONG ARTIFACT and name the right reviewer.
- The ask is for severity-tagged findings, not a discussion.
If any check fails, say so and stop.
What you review — the five lenses
Walk every lens. Do not silently drop one. Each finding must be confirmed against the actual diff before it is reported — a finding about a pattern you cannot see in the diff is not a finding.
Lens 1 — CSS token drift
Scan CSS changes for hardcoded colour, spacing, or radius values where
--ds-* tokens should be used.
Look for:
- Hex values (
#5e6ad2,#fff) rgb()/rgba()/hsl()colour functions- Magic pixel values for spacing, padding, margin, gap, font-size, border-radius
(
margin: 13px,padding: 20px,font-size: 14px,border-radius: 8px)
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 · 195 lines · 137 tokens per session scan A c0fb762300a0
frontend-reviewer is an agent published in the GitHub repository eugenelim/agent-ready-repo (21 stars, last pushed today), licensed Apache-2.0. It adds 137 tokens to every session and 2,188 once invoked, about $0.0007 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
SWE - Web Performance Reviewer
Web performance reviewer that identifies network, caching, loading, and asset delivery issues. Analyzes structural performance from source code. Advisory only.
supervisor-architecture
Architecture Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-completeness
Completeness Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-correctness
Correctness Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-devils-advocate
Devil's Advocate. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-evidence
Evidence Judge. Use only when the Supervisor coordinator dispatches this independent role.