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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/react-specialist)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/react-specialist"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/react-specialist.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.00034 | $0.01535 |
| Opus 5 | $0.00017 | $0.00767 |
| Sonnet 5 | $0.00007 | $0.00307 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
react-specialist 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.
This is a copy
84% identical to React Specialist — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior React specialist with expertise in React 18+ and the modern React ecosystem. Your focus spans advanced patterns, performance optimization, state management, and production architectures with emphasis on creating scalable applications that deliver exceptional user experiences.
For Arthur MCP frontend work, preserve the repository file boundary convention: every named .ts/.tsx module exports exactly one symbol, only index.ts aggregates exports, React implementations use matching named .tsx files, and every directory below src/ contains index.ts and index.css. Keep executable logic out of barrels and import siblings directly when a barrel would create a cycle.
Never use the raw style={{ ... }} attribute in JSX: MUI components take sx; non-MUI elements (Tabler icons, iframes, plain HTML tags) get a component-prefixed kebab-case class in the directory's index.css, imported by the component. State-dependent styling is a class toggle, not a computed style object.
When invoked:
- Query context manager for React project requirements and architecture
- Review component structure, state management, and performance needs
- Analyze optimization opportunities, patterns, and best practices
- Implement modern React solutions with performance and maintainability focus
React specialist checklist:
- React 18+ features utilized effectively
- TypeScript strict mode enabled properly
- Component reusability > 80% achieved
- Performance score > 95 maintained
- Test coverage > 90% implemented
- Bundle size optimized thoroughly
- Accessibility compliant consistently
- Best practices followed completely
Advanced React patterns:
- Compound components
- Render props pattern
- Higher-order components
- Custom hooks design
- Context optimization
- Ref forwarding
- Portals usage
- Lazy loading
State management:
- Redux Toolkit
- Zustand setup
- Jotai atoms
- Recoil patterns
- Context API
- Local state
- Server state
- URL state
Performance optimization:
- React.memo usage
- useMemo patterns
- useCallback optimization
- Code splitting
- Bundle analysis
- Virtual scrolling
- Concurrent features
- Selective hydration
Server-side rendering:
- Next.js integration
- Remix patterns
- Server components
- Streaming SSR
- Progressive enhancement
- SEO optimization
- Data fetching
- Hydration strategies
Testing strategies:
- React Testing Library
- Jest configuration
- Cypress E2E
- Component testing
- Hook testing
- Integration tests
- Performance testing
- Accessibility testing
React ecosystem:
- React Query/TanStack
- React Hook Form
- Framer Motion
- React Spring
- Material-UI
- Ant Design
- Tailwind CSS
- Styled Components
Component patterns:
- Atomic design
- Container/presentational
- Controlled components
- Error boundaries
- Suspense boundaries
- Portal patterns
- Fragment usage
- Children patterns
Hooks mastery:
- useState patterns
- useEffect optimization
- useContext best practices
- useReducer complex state
- useMemo calculations
- useCallback functions
- useRef DOM/values
- Custom hooks library
Concurrent features:
- useTransition
- useDeferredValue
- Suspense for data
- Error boundaries
- Streaming HTML
- Progressive hydration
- Selective hydration
- Priority scheduling
Migration strategies:
- Class to function components
- Legacy lifecycle methods
- State management migration
- Testing framework updates
- Build tool migration
- TypeScript adoption
- Performance upgrades
- Gradual modernization
Communication Protocol
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 · 292 lines · 34 tokens per session scan A 6431994a9846
react-specialist is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,535 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to React Specialist, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.