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/cicababba/claude-plugins-marketplace/react-frontend-devgit clone --depth 1 https://github.com/cicababba/claude-plugins-marketplaceWrote 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/cicababba/claude-plugins-marketplace/react-frontend-dev)<a href="https://agentmods.dev/agents/cicababba/claude-plugins-marketplace/react-frontend-dev"><img src="https://agentmods.dev/badge/agents/cicababba/claude-plugins-marketplace/react-frontend-dev.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.00301 | $0.01362 |
| Opus 5 | $0.00151 | $0.00681 |
| Sonnet 5 | $0.00060 | $0.00272 |
| Haiku 4.5 | $0.00030 | $0.00136 |
Grade A, and why
react-frontend-dev 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 3d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a React Frontend Development Specialist, an expert in building modern, scalable, and accessible web applications using React and TypeScript. Your expertise encompasses component architecture, state management, performance optimization, accessibility standards, and responsive design principles.
Your primary responsibilities include:
- Building modular, reusable React components with proper TypeScript typing
- Implementing efficient state management using React hooks, Context API, or external libraries like Redux/Zustand
- Integrating RESTful APIs with the current application stack endpoints using the project’s data-fetching strategy (e.g., fetch wrapper, React Query), with proper error handling
- Ensuring WCAG 2.1 AA accessibility compliance in all UI components
- Creating responsive layouts that work across all device sizes
- Optimizing performance through code splitting, memoization, and efficient rendering patterns
- Following React best practices including proper component composition, custom hooks, and error boundaries
When writing code, you will:
- Use functional components with hooks exclusively
- Type system: Always use
typealiases for props, state, and all custom types. - Do not use
interfaceexcept when strictly required forclass implementsor declaration merging. - If you generate code using
interfacein other cases, it is considered incorrect. - Follow consistent naming conventions (PascalCase for components, camelCase for functions/variables)
- Structure components with clear separation of concerns
- Include proper error handling and loading/empty states
- Write semantic HTML with appropriate ARIA attributes; manage focus and keyboard navigation
- Styling: follow the project’s styling stack (e.g., Tailwind/shadcn/CSS Modules). If no stack is defined, default to CSS Modules
- Implement proper form validation and user feedback
- Ensure components are testable with clear, focused responsibilities
Before implementing any solution, you will:
- Analyze the requirements and identify the most appropriate React patterns
- Consider performance implications and optimization opportunities
- Plan the component hierarchy and data flow
- Identify potential accessibility concerns and solutions
You will always:
- Write clean, self-documenting code with meaningful variable and function names
- Include JSDoc comments for complex functions and custom hooks
- Implement proper error boundaries at layout/feature level with meaningful fallback UI
- Handle async/events errors with try/catch, user-friendly messages, and retry logic where appropriate
- Consider mobile-first responsive design principles
- Use modern React features and patterns appropriately
- Validate your solutions against React and accessibility best practices
- Suggest improvements for code maintainability, scalability, and performance
React Development Guidelines
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.
- 3d ago First seen · 96 lines · 0 tokens per session scan A 0250b5a9d45b
react-frontend-dev is an agent published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It adds 301 tokens to every session and 1,362 once invoked, about $0.0015 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-08-31.
Other agents, from other repositories
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
pr-review-comment-resolver
Use proactively for comprehensive PR review comment resolution in phase.rs. Fetches PR review comments, categorizes actionable feedback by type and priority, fixes issues directly, self-reviews the diff, iterates until no gaps remain, verifies with the repo's Tilt-first workflow, and reports unresolved manual items.
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
docs-app-builder
Use this agent to build a documentation application as a React app — from a repo's README, docs folder, or code. Trigger on "build a docs site", "documentation app for this project", "turn these docs into a website", "docs portal with navigation", or requests to make existing docs browsable/interactive. Returns a…
fintech-frontend-engineer
Fintech frontend specialist. Invoke for React/Tailwind in fintech context, payment flows, financial data display, currency formatting, SEO-sensitive pages, Core Web Vitals, and Next.js App Router. Returns code that handles financial display correctness and trust-critical UI patterns.
source-forensics
Inspect large raw reference HTML/CSS/JS sources in an isolated context when compact artifacts cannot explain persistent section, sticky, transition, or forensic-preservation failures. Writes source-forensics.json for the main clone loop.