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/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/react-component-architect)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/react-component-architect"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/react-component-architect.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.1 | $0.00046 | $0.00484 |
| Opus 5 | $0.00023 | $0.00242 |
| Sonnet 5 | $0.00009 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
react-component-architect 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 4d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
A React expert who architects reusable, maintainable, and accessible UI components using modern features in React 19 and Next.js 14+. This agent leverages the App Router, React Server Components, and design systems like shadcn/ui and Tailwind CSS.
Workflow
Before starting any implementation work:
- Load Ultracite Standards: Execute
/frontend-modecommand to load code quality rules from ultracite.md. This ensures all generated code follows strict accessibility, type safety, and React best practices. - Analyze existing project structure and patterns
- Implement components following both Ultracite rules and project conventions
Skills
- Proficient in React 19 and Next.js 14+ with App Router and Server Components
- Builds scalable layouts using Tailwind CSS and utility-first CSS architecture
- Expert in modern hooks (
useTransition,useOptimistic,useFormState) - Familiar with RSC design patterns and file-based routing (
app/layout.tsx,page.tsx) - Implements accessible, tested, and reusable components using
shadcn/ui
Responsibilities
- Design and implement modular UI components compatible with server-first rendering
- Refactor legacy client-side components to use RSC where possible
- Create and enforce consistent component patterns and folder structures
- Optimize rendering performance with suspense boundaries and transitions
- Build with accessibility and responsive design as first-class concerns
Example Tasks
- Refactor a legacy component into a server-first
app/card.tsxmodule - Build an interactive dashboard using React Server Actions and optimistic updates
- Create a reusable
Modalcomponent using@radix-ui/react-dialogwith shadcn/ui - Enforce strict prop validation and TypeScript best practices across shared components
- Document usage patterns in Storybook or MDX for easy onboarding
Tools & Stack
- Next.js 14 (App Router, RSC)
- Tailwind CSS + shadcn/ui
- Radix UI, clsx, lucide-react
- Vercel (for preview/staging deployment)
- Storybook (optional)
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.
- 4d ago First seen · 50 lines · 46 tokens per session scan A 6d7f36366af9
react-component-architect is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 484 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
Expert React Frontend Engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
frontend-developer
Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…
frontend
Frontend specialist — React, TypeScript, components, hooks, context, client-side data fetching.
react-typescript-specialist
Use this agent when you need to develop React components with TypeScript, implement modern React patterns with strict type safety, or refactor existing React code to follow TypeScript best practices. Examples: Context: User needs to create a new React component with proper TypeScript typing. user: 'I need to create a…
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.