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 adonai-labs/agent-runway --skill skill-react-coregit clone --depth 1 https://github.com/adonai-labs/agent-runwayWrote 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/adonai-labs/agent-runway/skill-react-core)<a href="https://agentmods.dev/skills/adonai-labs/agent-runway/skill-react-core"><img src="https://agentmods.dev/badge/skills/adonai-labs/agent-runway/skill-react-core/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/adonai-labs/agent-runway/skill-react-core"><img src="https://agentmods.dev/badge/skills/adonai-labs/agent-runway/skill-react-core.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.00089 | $0.00729 |
| Opus 5.5 | $0.00036 | $0.00292 |
| Sonnet 5.5 | $0.00018 | $0.00146 |
| Haiku 4.5 | $0.00009 | $0.00073 |
Grade A, and why
react-core 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Core
How to invoke
After agent-runway add react, the skill is installed at .cursor/skills/react-core/. Use:
- Cursor:
@react-coreor ask a React question while editing*.tsx/*.jsx(rules auto-attach) - Claude Code: reference
.agent-runway/skills/react-core/SKILL.mdor ask in context of React files
Examples:
- How should I structure this feature's components?
- When should I use context vs Zustand vs React Query?
- How do I test this hook without rendering a component?
- Is this memoisation justified?
Not sure which skill to use? Start with
/start— it classifies intent and routes to the right skill.
Guiding principles
Simplicity first. React's mental model is already a good guide — follow it rather than fighting it.
- Start with the simplest state and structure that works; add layers only when complexity demands it
- Composition over configuration; small, focused components over large multi-responsibility ones
- SOLID applies: SRP means one reason to render, DIP via props and hooks rather than direct coupling
- DRY for business logic in hooks and services; duplication in JSX is often acceptable
- Measure before memoising —
React.memo,useMemo, anduseCallbackhave a cost; profile first - Accessibility is not optional — semantic HTML and ARIA are part of the implementation, not an afterthought
What this skill helps with
- Project and feature structure scaled to complexity
- Component patterns — functional, composition, compound, controlled/uncontrolled
- State management decisions — local state, context, Zustand, React Query
- Custom hooks — extracting logic, cleaning up, dependency management
- Testing with React Testing Library — components, hooks, context, async
- Security: XSS,
dangerouslySetInnerHTML, input validation - Accessibility: semantic HTML, ARIA, keyboard navigation, focus management
- Performance: memoisation strategy, code splitting, virtualisation
Skill files
| File | Contents |
|---|---|
| architecture.md | Project structure, feature organisation, routing, naming |
| patterns.md | Component patterns, hooks, state management decisions |
| testing.md | RTL setup, component tests, hook tests, MSW, accessibility |
| security.md | XSS, CSP, input validation, dependency audit |
| observability.md | Error boundaries, logging, performance monitoring |
| reference.md | Toolchain, Vite config, common commands |
What ships with it
6 files 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.
- 1mo ago First seen · 69 lines · 89 tokens per session scan A 86b347c36ab9
react-core is a skill published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 22d ago), licensed MIT. It adds 89 tokens to every session and 729 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
react-application-structure
Establishes or reviews the directory layout, feature boundaries, state design, routing approach, and data-fetching conventions for a React 18+ TypeScript application. Invoked when the user asks to structure a React app, set up a scalable architecture, or review React project organization.
next-application-structure
Establishes or reviews directory layout, server/client boundaries, routing, data-fetching strategy, and testing structure for Next.js 14+ App Router TypeScript applications. Invoked when the user asks to structure a Next app, set App Router conventions, or review architecture for React parity.
React Component Reviewer
Analyzes React components for performance, accessibility, and modern hook usage.
invest-architecture
Audit the project structure against ARCHITECTURE.md. Reads YOUR doctrine at runtime — layers, naming, stack, conventions — and checks the codebase against what YOU declared. Not a preset. Your rules, enforced.
invest-preflight
Quick reconnaissance pass on a codebase to establish project type, tech stack, structure, scale, and conventions before running deeper skills like /invest-manifest or /invest-repo-audit. Run this first on any unfamiliar repo.
invest-repo-audit
Perform a full quality, stability, and architecture audit of a codebase. Identifies broken features, dead code, spaghetti coupling, missing error handling, security gaps, performance problems, and technical debt. Produces a classified report with prioritized remediation.