react-component-builder

react-component-builder is an agent for Claude Code from vanessamarely/ai-playbook-reposito. It costs 19 tokens per session (1,106 once invoked), scanned A, original, MIT.

An agent that creates or updates React interface components using TypeScript and accessibility standards such as WCAG 2.2.

In plain words
What is it for?
Use it to build a named React component from a specification, place it in a chosen folder, and optionally add tests, Storybook documentation, or styles.
Why use it?
It reduces the manual work of setting up component files, typed properties, accessibility details, and related project files.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/vanessamarely/ai-playbook-reposito/react-component-builder
Clone the repo
git clone --depth 1 https://github.com/vanessamarely/ai-playbook-reposito

Made for: Claude Code.

Wrote 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.

agentmods badge for react-component-builder

README.md
[![agentmods](https://agentmods.dev/badge/agents/vanessamarely/ai-playbook-reposito/react-component-builder.svg)](https://agentmods.dev/agents/vanessamarely/ai-playbook-reposito/react-component-builder)
Your own site
<a href="https://agentmods.dev/agents/vanessamarely/ai-playbook-reposito/react-component-builder"><img src="https://agentmods.dev/badge/agents/vanessamarely/ai-playbook-reposito/react-component-builder.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,106 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.01106
Opus 5 $0.00010 $0.00553
Sonnet 5 $0.00004 $0.00221
Haiku 4.5 $0.00002 $0.00111

Measured 5d ago against content hash aa7187b4e955, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

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 5d 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.

ai-playbook/.claude/agents/react-component-builder.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

React Component Builder Agent

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

  1. Ensure componentName follows PascalCase convention.
  2. Verify targetFolder exists and is within project scope.
  3. Check for naming conflicts with existing components.

Step 2: Load Skill

Read: .claude/skills/react-components/SKILL.md

Follow the procedures defined in that skill.

Step 3: Generate Component Structure

  1. Create the component file at <targetFolder>/<componentName>.tsx.
  2. Define TypeScript interface for props with explicit types:
    • Use discriminated unions for variant props
    • Mark readonly properties appropriately
    • Use React.ReactNode for 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
    }
    
  3. Implement the component with semantic HTML.
  4. Add accessibility attributes (ARIA roles, labels, keyboard handlers).
  5. Use explicit return type: const Component = (props: Props): JSX.Element => { ... }
  6. Avoid any types - use unknown with type guards if needed.

Refer to:

  • .claude/skills/react-components/references/a11y-wcag22.md for WCAG 2.2 requirements
  • .github/copilot-instructions.md for TypeScript best practices

Step 4: Apply Project-Specific Overrides

Read the full file on GitHub · 143 lines

Changes

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.

  1. 5d ago First seen · 143 lines · 19 tokens per session scan A aa7187b4e955

Subscribe to this mod's changes

react-component-builder is an agent published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 1,106 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

react18-class-surgeon

Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…

github/awesome-copilot · 81 tokens

react19-auditor

Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.

github/awesome-copilot · 61 tokens

ci-watcher

Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.

nrwl/nx · 37 tokens

merge-conflict-resolver

Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…

module-federation/core · 0 tokens

tauri-axum-parity-checker

Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…

jhlee0409/claude-code-history-viewer · 112 tokens

domain

How the engineering skills should consume this repo's domain documentation when exploring the codebase.

jhlee0409/claude-code-history-viewer · 0 tokens