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 skills/aaronbassett/agent-foundry/react-componentsnpx skills add aaronbassett/agent-foundry --skill react-componentsgit clone --depth 1 https://github.com/aaronbassett/agent-foundryWhat 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.00096 | $0.00603 |
| Opus 5 | $0.00048 | $0.00302 |
| Sonnet 5 | $0.00019 | $0.00121 |
| Haiku 4.5 | $0.00010 | $0.00060 |
Grade A, and why
devs:react-components 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Components — House Style
The authoring contract for components in this codebase family. Verify package facts against npm and installed types — never from trained knowledge.
The contract in one paragraph
Components split into a Container (data: hooks, queries, callbacks) and a View (pure props-in/JSX-out). Views model exactly four canonical states — loading, empty, error, ready — as a discriminated union; every View handles all four and stories cover all four. Interactive elements are real elements with accessible names, and tests query by role.
Reference routing
| Reference | Use when |
|---|---|
| patterns.md | The container/presenter contract, four-state union, composition rules |
| styling.md | Tailwind v4 CSS-first tokens, the cn() utility, variants without a variant library |
| headless-components.md | Building headless primitives: compound components, asChild, keyboard support |
| forms.md | React Hook Form + zod house pattern and file convention |
| accessibility.md | The a11y floor for every component |
| storybook.md | CSF3 stories, play functions, docs, network states |
| error-handling.md | Error boundaries, classification into the four-state contract |
| web3-ui.md | ONLY for dapp work: addresses, token amounts, approvals, secret display |
Boundaries
- devs:react-core owns runtime idioms, state/data architecture, application security (XSS canonical), project layout, and the React package list.
- devs:typescript-core owns test mechanics (vitest, Testing Library, userEvent), language, and generic packages.
- Package selection: check
package.jsonfirst — the installed stack is the convention; then react-core'spackages.md.
Scaffold script
node ${CLAUDE_SKILL_DIR}/scripts/scaffold-component.mjs <featureName> <ComponentName> — generates the api-hook stub, Container, four-state View, stories, and test under src/features/<featureName>/; validates names, and refuses to overwrite existing files. Generated code passes strict typecheck and its generated test.
What ships with it
9 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.
- references/accessibility.md 2.3 KB
- references/error-handling.md 3.9 KB
- references/forms.md 4.8 KB
- references/headless-components.md 12 KB
- references/patterns.md 4.4 KB
- references/storybook.md 4.5 KB
- references/styling.md 2.7 KB
- references/web3-ui.md 5.4 KB
- scripts/scaffold-component.mjs 7.1 KB runs code
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 · 36 lines · 96 tokens per session scan A 9c1553921c03
devs:react-components is a skill published in the GitHub repository aaronbassett/agent-foundry (4 stars, last pushed 17d ago), licensed MIT. It adds 96 tokens to every session and 603 once invoked, about $0.0005 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…
row-selection
Maintain rowSelection ID state with stable getRowId, single, multi, subrow, and Shift-range rules, selected row models, handler anchors, and manual-pagination semantics. Load when implementing getToggleSelectedHandler, enableRowRangeSelection, selectChildren, deselectParents, or selected IDs that outlive loaded Row…
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.
wrdn-effect-promise-exit
Replace React/effect-atom mutation handlers that use promise-mode plus try/catch with promiseExit and explicit Exit handling. Use when lint or review flags try/catch around useAtomSet mutation calls, especially UI handlers that set error/busy state after a failed mutation.
assistant-ui-primitives
Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive. Use when customizing chat UI components.