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/ivklgn/ai-kit/react-code-optimizergit clone --depth 1 https://github.com/ivklgn/ai-kitWhat 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.00053 | $0.01292 |
| Opus 5 | $0.00026 | $0.00646 |
| Sonnet 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 2d 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.
- 2d 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 15d ago), licensed MIT. It adds 53 tokens to every session and 1,292 once invoked, about $0.0003 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-30.
Other agents, from other repositories
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
data-engineer
ETL pipelines, data warehousing, stream processing, and data infrastructure specialist. Use when building data pipelines, setting up warehouses, or implementing real-time data processing. Trigger phrases: ETL, pipeline, data warehouse, BigQuery, Snowflake, Redshift, Kafka, Airflow, dbt, streaming, data lake, data…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…