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 CODE-SAURABH/OpenSkills --skill react-developmentgit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWrote 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/code-saurabh/openskills/react-development)<a href="https://agentmods.dev/skills/code-saurabh/openskills/react-development"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/react-development/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/skills/code-saurabh/openskills/react-development"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/react-development.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.00051 | $0.03555 |
| Opus 5.5 | $0.00020 | $0.01422 |
| Sonnet 5.5 | $0.00010 | $0.00711 |
| Haiku 4.5 | $0.00005 | $0.00356 |
Grade A, and why
react-development 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Development
Act as the React engineer responsible for an interface that remains correct through loading, failure, navigation, concurrent rendering, assistive technology, and future product changes. Build around user tasks and data ownership, not component count or hook cleverness.
Execution Workflow
- Inspect the app architecture. Identify React version, framework/rendering model, router, styling system, component library, state/query libraries, test stack, API conventions, and existing accessibility patterns.
- Model the flow and state. Define the user task, server/client state, transitions, permissions, loading/empty/error/success states, URL state, and mutation recovery before coding.
- Compose the interface. Create focused components around meaningful boundaries. Keep fetch and mutation ownership close to the feature boundary; pass explicit props and callbacks.
- Implement accessible behavior. Use semantic HTML, native controls where possible, keyboard interactions, focus management, and clear feedback.
- Verify runtime behavior. Test primary and failure paths, inspect responsive layouts, and check for hydration, render, and interaction regressions.
Step 0: Ground the Feature in a User Flow
Before creating components, establish:
- User job: What does a person need to see, decide, or complete?
- Route and rendering model: Which route owns this feature and is it server-rendered, client-rendered, streamed, or static?
- State ownership: What is server state, URL state, local draft state, shared UI state, and derived state?
- Permissions and outcomes: Who can perform the action, what succeeds, and what can fail or be retried?
- Acceptance proof: Which keyboard flow, viewport, data state, and test demonstrate completion?
Inspect the route, nearby components, styling/tokens, data/query layer, router, existing primitives, and tests before adding a new pattern. Preserve an intentional design system; do not create a competing button, dialog, fetch wrapper, or state store for one feature.
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 · 273 lines · 51 tokens per session scan A 182030123802
react-development is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (3 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 3,555 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-31.
Other skills, from other repositories
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.
cloudflare-nextjs
Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare). Use for SSR/ISR/SSG/App or Pages Router, getCloudflareContext, bindings (D1/R2/KV/AI/Hyperdrive), caching tiers, skew protection, multi-worker, custom worker, env vars, or worker…
auto-animate
AutoAnimate (@formkit/auto-animate) zero-config animations for React. Use for list transitions, accordions, toasts, or encountering SSR errors, animation libraries complexity.
base-ui-react
MUI Base UI unstyled React components with Floating UI. Use for accessible components, Radix UI migration, render props API, or encountering positioning, popup, v1.0 rc / pre-GA issues.
bun-nextjs
This skill should be used when the user asks about "Next.js with Bun", "Bun and Next", "running Next.js on Bun", "Next.js development with Bun", "create-next-app with Bun", or building Next.js applications using Bun as the runtime.
bun-react-ssr
Use when building server-rendered React with Bun, including streaming SSR, hydration, renderToString, or custom SSR without a framework.