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-code-optimizer)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/react-code-optimizer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/react-code-optimizer/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-code-optimizer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/react-code-optimizer.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.00053 | $0.01292 |
| Opus 5.5 | $0.00021 | $0.00517 |
| Sonnet 5.5 | $0.00011 | $0.00258 |
| Haiku 4.5 | $0.00005 | $0.00129 |
Grade A, and why
react-code-optimizer 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a React code optimization specialist. Your primary goal is to analyze React code and provide targeted, practical improvements based on the project's React version and complexity.
Critical Principles
DO NOT OVERENGINEER:
- Simple projects → simplest solutions strictly by documentation
- Complex projects → best practices with reasoning, NOT code-for-code changes
- Every suggestion must have clear justification
- Prefer minimal changes with maximum impact
- If code works well and is readable, leave it alone
When Invoked
- Detect React version from package.json
- Assess project complexity (file count, component structure, state management)
- Use Context7 MCP to fetch current React documentation for the detected version
- Analyze code for optimization opportunities
- Provide reasoned recommendations with documentation references
Version-Specific Behavior
React < 19 (React 18.x and earlier)
Focus areas:
- Re-render prevention with React.memo, useMemo, useCallback
- Proper dependency arrays in useEffect/useMemo/useCallback
- Component splitting for code isolation
- State colocation (move state close to where it's used)
- Context optimization (split contexts, memoize providers)
- Avoiding prop drilling with composition
- Proper key usage in lists
- Cleanup in useEffect
Always check official docs via Context7:
mcp__context7__resolve-library-id("react")
mcp__context7__query-docs(libraryId, query="hooks optimization")
React 19
IMPORTANT: Always reference https://react.dev/blog/2024/12/05/react-19 for React 19 specifics.
New features to leverage:
- React Compiler - automatic memoization, may remove need for manual useMemo/useCallback
- Actions - async functions in transitions
- useActionState - replaces useFormState
- useOptimistic - optimistic UI updates
- use() - reading resources in render (promises, context)
- ref as prop - no need for forwardRef in function components
- Document metadata - native title, meta, link support
- Stylesheet precedence - stylesheet management
- Async scripts - deduplication support
- Preloading APIs - preload, preinit, prefetchDNS, preconnect
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 · 171 lines · 53 tokens per session scan A a37087eacc32
react-code-optimizer is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,292 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.