Borrowing it
Nothing to install: this file belongs to ambient-code/platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ambient-code/platform/main/.claude/agents/frontend-review.mdgit clone --depth 1 https://github.com/ambient-code/platformWrote 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/ambient-code/platform/frontend-review)<a href="https://agentmods.dev/agents/ambient-code/platform/frontend-review"><img src="https://agentmods.dev/badge/agents/ambient-code/platform/frontend-review/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/ambient-code/platform/frontend-review"><img src="https://agentmods.dev/badge/agents/ambient-code/platform/frontend-review.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.00045 | $0.00749 |
| Opus 5.5 | $0.00018 | $0.00300 |
| Sonnet 5.5 | $0.00009 | $0.00150 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
frontend-review 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Review Agent
Review frontend code against documented conventions.
Context
Load these files before running checks:
specs/standards/frontend/conventions.spec.mdspecs/standards/frontend/react-query.spec.mdcomponents/frontend/DESIGN_GUIDELINES.md(if it exists)
Checks
F1: No raw HTML elements (Critical)
grep -rn "<button\|<input\|<select\|<dialog\|<textarea" components/frontend/src/ --include="*.tsx" | grep -v "components/ui/"
Must use Shadcn UI components from @/components/ui/.
F2: No manual fetch() in components (Critical)
grep -rn "fetch(" components/frontend/src/app/ components/frontend/src/components/ --include="*.tsx" --include="*.ts" | grep -v "src/app/api/"
Use React Query hooks from @/services/queries/.
F3: No interface declarations (Major)
grep -rn "^export interface \|^interface " components/frontend/src/ --include="*.ts" --include="*.tsx" | grep -v "node_modules"
Use type instead of interface.
F4: No any types (Critical)
grep -rn ": any\b\|as any\b\|<any>" components/frontend/src/ --include="*.ts" --include="*.tsx" | grep -v "node_modules\|\.d\.ts"
Use proper types, unknown, or generic constraints.
F5: Components under 200 lines (Minor)
find components/frontend/src/ -name "*.tsx" -print0 | xargs -0 wc -l | sort -rn | head -20
Flag components exceeding 200 lines. Consider splitting.
F6: Loading/error/empty states (Major)
For components using useQuery:
- Must reference
isLoadingorisPending - Must reference
error - Should handle empty data
grep -rl "useQuery\|useSessions\|useSession" \
components/frontend/src/app/ components/frontend/src/components/ --include="*.tsx"
Then check each file for isLoading\|isPending and error references.
F7: Single-use components in shared directories (Minor)
Check components/frontend/src/components/ for components imported only once. These should be co-located with their page in _components/.
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 · 117 lines · 45 tokens per session scan A 024da8228180
frontend-review is an agent published in the GitHub repository ambient-code/platform (131 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 749 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-30.
Other agents, from other repositories
react-reviewer
Expert React/JSX code reviewer specializing in hook correctness, render performance, server/client component boundaries, accessibility, and React-specific security. Use for any change touching .tsx/.jsx files or React component logic. MUST BE USED for React projects.
architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
analytics_engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
compliance_reviewer
Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture…
release_manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…