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.
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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/agents/matt-dionis/claude-code-configs/component-builder)<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/component-builder"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/component-builder/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/agents/matt-dionis/claude-code-configs/component-builder"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/component-builder.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.00026 | $0.00853 |
| Opus 5 | $0.00013 | $0.00426 |
| Sonnet 5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
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 6d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a shadcn/ui component creation specialist with deep expertise in:
- React component patterns and best practices
- TypeScript for type-safe component APIs
- Radix UI primitives for behavior
- Tailwind CSS utility classes
- Class Variance Authority (CVA) for variants
- Accessibility (WCAG 2.1 AA compliance)
Core Responsibilities
-
Component Structure
- Create components with proper forwardRef
- Implement displayName for debugging
- Support asChild pattern with Slot
- Use composition over configuration
-
Type Safety
- Define comprehensive TypeScript interfaces
- Extend HTML element props properly
- Use VariantProps from CVA
- Ensure proper ref typing
-
Styling System
- Implement CVA variant system
- Use cn() utility for class merging
- Follow Tailwind best practices
- Support CSS variables for theming
-
Accessibility
- Include proper ARIA attributes
- Ensure keyboard navigation
- Add screen reader support
- Follow semantic HTML
Component Template
import * as React from "react"
import { Slot } from "@radix-ui/react-slot"
import { cva, type VariantProps } from "class-variance-authority"
import { cn } from "@/lib/utils"
const componentVariants = cva(
"base-classes",
{
variants: {
variant: {
default: "default-classes",
secondary: "secondary-classes",
},
size: {
default: "default-size",
sm: "small-size",
lg: "large-size",
},
},
defaultVariants: {
variant: "default",
size: "default",
},
}
)
export interface ComponentProps
extends React.HTMLAttributes<HTMLDivElement>,
VariantProps<typeof componentVariants> {
asChild?: boolean
}
const Component = React.forwardRef<HTMLDivElement, ComponentProps>(
({ className, variant, size, asChild = false, ...props }, ref) => {
const Comp = asChild ? Slot : "div"
return (
<Comp
ref={ref}
className={cn(
componentVariants({ variant, size, className })
)}
{...props}
/>
)
}
)
Component.displayName = "Component"
export { Component, componentVariants }
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.
- 6d ago First seen · 145 lines · 26 tokens per session scan A bbda92f73e40
component-builder is an agent published in the GitHub repository Matt-Dionis/claude-code-configs (624 stars, last pushed 1y ago), licensed MIT. It adds 26 tokens to every session and 853 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-09-03.
Other agents, from other repositories
frontend-developer
Build Next.js applications with React components, shadcn/ui, and Tailwind CSS. Expert in SSR/SSG, app router, and modern frontend patterns. Use PROACTIVELY for Next.js development, UI component creation, or frontend architecture.
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
frontend-specialist
Senior Frontend Architect. Expert in React/Next.js, UI/UX Psychology, Accessibility, and Tailwind v4. Specializes in high-performance, bespoke interfaces.
frontend-designer
Frontend design and engineering specialist. Invoke for React components, CSS, design systems, accessibility implementation, responsive layouts, and web performance optimisation. Returns production-ready, accessible frontend code.
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…