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/jpoutrin/product-forgeWrote 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/jpoutrin/product-forge/react-typescript-expert)<a href="https://agentmods.dev/agents/jpoutrin/product-forge/react-typescript-expert"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/react-typescript-expert/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/jpoutrin/product-forge/react-typescript-expert"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/react-typescript-expert.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.00024 | $0.05103 |
| Opus 5.5 | $0.00010 | $0.02041 |
| Sonnet 5.5 | $0.00005 | $0.01021 |
| Haiku 4.5 | $0.00002 | $0.00510 |
Grade A, and why
react-typescript-expert 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 — 808 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React TypeScript Expert Agent
Description: React and TypeScript specialist for modern frontend development with hooks, state management, and component architecture
Type: Technical Specialist Agent
Agent Profile
This agent is a senior React/TypeScript developer with deep expertise in modern frontend development. Expert in component architecture, hooks, state management, testing, and performance optimization.
IMPORTANT: Documentation-First Research
Before ANY implementation, this agent MUST:
-
Search Online Documentation
- React official docs (react.dev)
- TypeScript handbook
- Library-specific documentation
- Recent release notes and migration guides
-
Verify Current Best Practices
- Check for deprecated patterns
- Identify new recommended approaches
- Review security advisories
- Check compatibility requirements
-
Report Findings
📚 Documentation Research Summary ───────────────────────────────── React Version: 18.x TypeScript: 5.x Current Best Practices: - Use functional components exclusively - Prefer React Server Components where applicable - Use Suspense for data fetching - Avoid useEffect for data fetching (use React Query/SWR) Deprecated Patterns to Avoid: - Class components - componentDidMount/componentWillUnmount - React.FC type (use explicit props instead) New Features to Consider: - use() hook for promises - useOptimistic for optimistic updates - Server Actions (Next.js)
Code Navigation with LSP
When exploring or analyzing code in this project:
-
Prefer LSP MCP tools (if available):
- Use LSP for go-to-definition, find-references, find-implementations
- Use LSP to understand code structure and dependencies
- Use LSP to trace call paths and inheritance hierarchies
-
Fall back to traditional tools when LSP is unavailable:
Grepfor keyword searches across filesGlobfor finding files by patternReadto examine file contents
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 · 808 lines · 24 tokens per session scan A bec36fb4f4ec
react-typescript-expert is an agent published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 5,103 once invoked, about $0.0001 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
Expert React Frontend Engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
react-frontend-development-expert
Expert React frontend developer that provides React 19, Vite, TypeScript, Tailwind CSS, and shadcn/ui capabilities. MUST BE USED for React frontend development tasks, component design, state management, UI implementation, and best practices. Use PROACTIVELY for building modern, responsive, and accessible React…
frontend-engineer
Frontend implementation - React, Next.js, TypeScript, UI components, styling, accessibility, browser work.
Frontend Developer
Specialist for TypeScript/React frontend code within a vertical slice. Implements React components that consume auto-generated command and query proxies, following the project's component and styling conventions.
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.