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-specialistgit 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.00045 | $0.01424 |
| Opus 5 | $0.00023 | $0.00712 |
| Sonnet 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 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 — 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.
- 2d 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 15d ago), licensed MIT. It adds 45 tokens to every session and 1,424 once invoked, about $0.0002 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…