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 skills add JakubMikolajek/codex-skills-collection --skill reactgit clone --depth 1 https://github.com/JakubMikolajek/codex-skills-collectionWrote 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/skills/jakubmikolajek/codex-skills-collection/react)<a href="https://agentmods.dev/skills/jakubmikolajek/codex-skills-collection/react"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/react.svg" alt="Measured on agentmods" 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.00050 | $0.01414 |
| Opus 5 | $0.00025 | $0.00707 |
| Sonnet 5 | $0.00010 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
react 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 8d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Implementation Patterns
Use this skill to build React UI that is predictable, composable, and easy to reason about under change.
When to Use
- Building, refactoring, or debugging React components, hooks, or client-side interaction flows
- Reviewing React code for component design, state management, or rendering correctness
- Implementing forms, interactive widgets, or data-driven UI with React
- Optimizing React rendering performance (memoization, re-render analysis)
When NOT to Use
- Task is about Next.js-specific routing, SSR, or server components — use
react-nextjs(load alongsidereact) - Task is about shadcn/ui component styling or Tailwind class hygiene — use
shadcn-tailwind(load alongsidereact) - Task is about Vue, Nuxt, or SwiftUI — use the appropriate framework skill
Delivery Workflow
Use the checklist below and track progress:
React progress:
- [ ] Step 1: Discover project conventions, routing, and state boundaries
- [ ] Step 2: Define component API and ownership of state
- [ ] Step 3: Implement rendering and interaction flow
- [ ] Step 4: Control effects, async state, and performance
- [ ] Step 5: Verify accessibility and tests
Component Design
- Prefer small focused components with a stable public API.
- Keep state as close as possible to where it is used, but no closer than clarity allows.
- Lift state only when multiple consumers genuinely need shared ownership.
- Separate presentational pieces from data orchestration when complexity grows.
- Reuse existing design-system and shared primitives before creating new ones.
Component Composition
- Use compound components for complex widgets with shared context (Select, Tabs, Accordion).
- Always use
forwardRefwhen building components that wrap native HTML elements or Radix primitives — consumers may need ref access for focus management, scrolling, or measurement. - Prefer controlled components when the parent needs to read or reset state. Default to uncontrolled when internal state is sufficient and the parent does not observe it.
- Keep one component per file. Export sub-components from the same file only for compound patterns.
- Do not create wrapper components that just pass all props through — that adds indirection without value.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 145 lines · 50 tokens per session scan A adb85cf2f37d
react is a skill published in the GitHub repository JakubMikolajek/codex-skills-collection (5 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 1,414 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-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
menu-testing-ssr
Server rendering and testing for react-horizontal-scrolling-menu: the library is client-only ('use client' required in React Server Components, else "createContext is not a function"), SSR first paint is controlled by the useIsVisible defaultValue argument (canonical ('first', true) / ('last', false))…