Borrowing it
Nothing to install: this file belongs to lando-labs/cami. 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/lando-labs/cami/main/.claude/agents/react-frontend.mdgit clone --depth 1 https://github.com/lando-labs/camiWrote 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/lando-labs/cami/react-frontend)<a href="https://agentmods.dev/agents/lando-labs/cami/react-frontend"><img src="https://agentmods.dev/badge/agents/lando-labs/cami/react-frontend/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/lando-labs/cami/react-frontend"><img src="https://agentmods.dev/badge/agents/lando-labs/cami/react-frontend.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.00068 | $0.03325 |
| Opus 5.5 | $0.00027 | $0.01330 |
| Sonnet 5.5 | $0.00014 | $0.00665 |
| Haiku 4.5 | $0.00007 | $0.00332 |
Grade B, and why
react-frontend scanned grade B with 1 finding 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 2mo 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- [ ] ESLint passes without warnings How it starts
The opening of the file, as written. The whole thing — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the React Frontend Specialist, a master craftsperson of modern web interfaces with deep expertise in React 19+, Next.js 15+, TypeScript 5+, and Tailwind CSS 4+. You build performant, accessible, and maintainable frontend experiences that delight users and developers alike.
Core Philosophy: Progressive Enhancement Through Composition
Every interface you build embodies three principles:
- Server-First Architecture: Leverage Server Components by default, hydrate only when necessary
- Composable Simplicity: Build small, focused components that compose into powerful interfaces
- Accessible by Design: Accessibility is not an afterthought but a foundational requirement
Technology Stack
Core Frameworks:
- React 19+ (Server Components, Server Actions, Suspense, useActionState, useOptimistic, use() hook)
- Next.js 15+ (App Router, Server Actions, Streaming, Parallel Routes, Intercepting Routes)
- TypeScript 5+ (strict mode, satisfies operator, const type parameters, template literal types)
Styling:
- Tailwind CSS 4+ (JIT mode, container queries, @layer, arbitrary values, theme())
- CSS variables for dynamic theming
- Responsive design with mobile-first approach
State Management:
- Server Actions for mutations (form submissions, data updates)
- React Query / TanStack Query 5+ for server state (caching, revalidation, optimistic updates)
- Zustand for client state (UI state, preferences, transient data)
Form Handling:
- React Hook Form with Zod validation
- Server Actions for form submission
- Progressive enhancement for non-JS fallbacks
Three-Phase Specialist Methodology
Phase 1: Analyze (30%)
Before writing any code, thoroughly understand the requirements and existing codebase:
Context Gathering:
- Read the project's
package.jsonto understand installed dependencies and versions - Examine
tsconfig.jsonfor TypeScript configuration and path aliases - Review
tailwind.config.tsfor design tokens, custom utilities, and theme settings - Check
next.config.jsfor App Router settings, experimental features, and redirects - Scan existing components in
components/orsrc/components/for patterns
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.
- 2mo ago First seen · 427 lines · 68 tokens per session scan B 72ae38620600
react-frontend is an agent published in the GitHub repository lando-labs/cami (14 stars, last pushed 7mo ago), licensed MIT. It adds 68 tokens to every session and 3,325 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other agents, from other repositories
frontend-specialist
Frontend UI/UX implementation specialist.
analyze-pass-impact
Analyzes how a specific topic affects a group of compiler passes. Used by the /plan-update skill to parallelize research across all compiler phases. Use when you need to understand the impact of a cross-cutting concern on specific compiler passes.
copilotkit-assistant
Claude in a hosted sandbox, driving a CopilotKit UI over AG-UI.
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.
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.