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 vanessamarely/ai-playbook-reposito --skill react-component-buildergit clone --depth 1 https://github.com/vanessamarely/ai-playbook-repositoWrote 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/vanessamarely/ai-playbook-reposito/react-component-builder)<a href="https://agentmods.dev/skills/vanessamarely/ai-playbook-reposito/react-component-builder"><img src="https://agentmods.dev/badge/skills/vanessamarely/ai-playbook-reposito/react-component-builder.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.00047 | $0.01111 |
| Opus 5 | $0.00023 | $0.00556 |
| Sonnet 5 | $0.00009 | $0.00222 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade A, and why
react-component-builder 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: React Component Builder
Purpose
Create or modify React components with TypeScript, ensuring accessibility compliance and adherence to project conventions.
Inputs
componentName: Name of the component (PascalCase).specification: Component behavior, props, and requirements.targetFolder: Location within the project for the new component.
Outputs
- Component file (
.tsx). - Optional: associated test file, Storybook story, or style file.
- Verification command suggestions.
Procedure
Step 1: Validate Inputs
- Ensure
componentNamefollows PascalCase convention. - Verify
targetFolderexists and is within project scope. - Check for naming conflicts with existing components.
Step 2: Load Skill
Read: .agents/skills/react-components/SKILL.md
Follow the procedures defined in that skill.
Step 3: Generate Component Structure
- Create the component file at
<targetFolder>/<componentName>.tsx. - Define TypeScript interface for props with explicit types:
- Use discriminated unions for variant props
- Mark readonly properties appropriately
- Use
React.ReactNodefor children - Provide JSDoc comments for complex props
- Example:
interface ButtonProps { /** Visual style variant */ variant: 'primary' | 'secondary' | 'danger' /** Button click handler */ onClick: (event: React.MouseEvent<HTMLButtonElement>) => void /** Disable button interaction */ disabled?: boolean children: React.ReactNode } - Implement the component with semantic HTML.
- Add accessibility attributes (ARIA roles, labels, keyboard handlers).
- Use explicit return type:
const Component = (props: Props): JSX.Element => { ... } - Avoid
anytypes - useunknownwith type guards if needed.
Refer to:
.agents/skills/react-components/references/a11y-wcag22.mdfor WCAG 2.2 requirements../../../AGENTS.mdfor TypeScript best practices
Step 4: Apply Project-Specific Overrides
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 · 141 lines · 47 tokens per session scan A dc5bb5cefa52
react-component-builder is a skill published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,111 once invoked, about $0.0002 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))…