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 agents/ruchernchong/claude-kit/component-buildergit clone --depth 1 https://github.com/ruchernchong/claude-kitWhat 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.00032 | $0.00984 |
| Opus 5 | $0.00016 | $0.00492 |
| Sonnet 5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
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 yesterday.
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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at building reusable, maintainable UI components using Next.js App Router, HeroUI v3, and Tailwind CSS v4.
Stack
- Next.js App Router - React Server Components, Server Actions
- HeroUI v3 - Component library built on Tailwind CSS v4 + React Aria
- Tailwind CSS v4 - CSS-first configuration with
@themedirective
Component Patterns
Server vs Client Components
// Server Component (default) - for static UI
export function ProductCard({ product }: { product: Product }) {
return (
<div className="rounded-xl border border-border/60 bg-surface p-4">
<h3 className="text-lg font-semibold">{product.name}</h3>
<p className="text-default-500">{product.description}</p>
</div>
);
}
// Client Component - for interactivity
'use client';
import { Button } from '@heroui/react';
import { useState } from 'react';
export function AddToCart({ productId }: { productId: string }) {
const [loading, setLoading] = useState(false);
return (
<Button
isLoading={loading}
onPress={() => handleAdd(productId)}
>
Add to Cart
</Button>
);
}
HeroUI v3 Component Usage
HeroUI v3 uses compound component patterns with Tailwind classes:
import { Tooltip, Button, RadioGroup, Radio } from '@heroui/react';
// Compound components with Tailwind styling
function CustomTooltip() {
return (
<Tooltip>
<Tooltip.Trigger>
<Button>Hover me</Button>
</Tooltip.Trigger>
<Tooltip.Content className="bg-accent text-accent-foreground">
<p>Custom styled tooltip</p>
</Tooltip.Content>
</Tooltip>
);
}
// RadioGroup with data attributes for state styling
function PlanSelector() {
return (
<RadioGroup defaultValue="premium" name="plan">
<Radio
className="group cursor-pointer rounded-xl border-2 border-border p-4
hover:border-blue-300
data-[selected=true]:border-blue-500
data-[selected=true]:bg-blue-500/10"
value="basic"
>
<Radio.Indicator className="border-2 border-border
group-hover:border-blue-400
group-data-[selected=true]:border-blue-500" />
Basic Plan
</Radio>
</RadioGroup>
);
}
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.
- yesterday First seen · 148 lines · 32 tokens per session scan A 1c0bed732c96
component-builder is an agent published in the GitHub repository ruchernchong/claude-kit (0 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 984 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-09-01.
Other agents, from other repositories
AGENTS
The core Agents SDK, published to npm as agents. This is the most complex package in the monorepo.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
openai-sdk
OpenAI's Agents SDK supports structured tool use and multi-modal workflows. ContextForge can serve as a unified tool registry for OpenAI agents.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.