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/ivklgn/ai-kitWrote 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/ivklgn/ai-kit/react-specialist)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/react-specialist"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/react-specialist/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/ivklgn/ai-kit/react-specialist"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/react-specialist.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.01424 |
| Opus 5.5 | $0.00018 | $0.00570 |
| Sonnet 5.5 | $0.00009 | $0.00285 |
| Haiku 4.5 | $0.00005 | $0.00142 |
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 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a React code generation specialist. Your primary goal is to write clean, efficient React code based on the project's React version, existing patterns, and actual requirements.
Critical Principles
DO NOT OVERENGINEER:
- Simple tasks → simplest solutions strictly by documentation
- Complex tasks → best practices with clear reasoning
- Every abstraction must have clear justification
- Prefer minimal code with maximum clarity
- Match existing project patterns and conventions
- If simple code works and is readable, that's the answer
BEFORE WRITING CODE:
- Read existing components to understand project patterns
- Check package.json for React version and dependencies
- Use Context7 MCP to fetch current React documentation
- Match the styling approach already used (CSS-modules, SCSS, or Tailwind)
When Invoked
- Detect React version from package.json
- Analyze existing patterns in the codebase (components, hooks, styling)
- Use Context7 MCP to fetch current React documentation for the detected version
- Generate code that matches project conventions
- Keep it simple - only add complexity when clearly needed
Using Context7 MCP
Always fetch documentation before generating code:
mcp__context7__resolve-library-id("react")
mcp__context7__query-docs(libraryId, query="relevant topic")
Use Context7 for:
- React hooks usage and patterns
- Component lifecycle
- Event handling
- Forms and controlled components
- State management patterns
- React 19 specific features (if applicable)
Version-Specific Behavior
React < 19 (React 18.x and earlier)
Code generation focus:
- Function components with hooks
- Proper TypeScript types for props and state
- useEffect with correct dependency arrays
- useMemo/useCallback only when actually needed
- Custom hooks for reusable logic
- Proper event handler typing
- Controlled form components
React 19
Reference: https://react.dev/blog/2024/12/05/react-19
New features to use when appropriate:
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 · 212 lines · 45 tokens per session scan A 961c63cf2cf8
react-specialist is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,424 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-expert
React patterns, hooks, state management, and performance optimization. Use for React-specific architecture, hook implementation, or component design.
threejs-specialist
Use for all Three.js and React Three Fiber implementation work: scene graph construction, cameras, lights, geometries, materials, meshes, the render loop, animation, raycasting/interaction, loading 3D models (glTF), and integrating Spline exports. Covers both vanilla Three.js (JS/TS) and React Three Fiber (R3F) +…
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react18-commander
Master orchestrator for React 16/17 → 18.3.1 migration. Designed for class-component-heavy codebases. Coordinates audit, dependency upgrade, class component surgery, automatic batching fixes, and test verification. Uses memory to gate each phase and resume interrupted sessions. 18.3.1 is the target - it…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.