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/commands/matt-dionis/claude-code-configs/create-variant)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/create-variant"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/create-variant.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.00012 | $0.00478 |
| Opus 5 | $0.00006 | $0.00239 |
| Sonnet 5 | $0.00002 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
create-variant 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 3d 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.
What it actually says
Add a new variant to an existing shadcn/ui component using CVA (class-variance-authority).
Instructions
- Locate the component file in
components/ui/[component].tsx - Find the existing CVA variants configuration
- Add the new variant to the appropriate variant type
- Update TypeScript types if needed
- Provide usage example of the new variant
Arguments
component-name: The component to modify (e.g.,button,card)variant-type: The type of variant (variant,size, or custom)variant-name: The name of the new variant
Example
If the user says: /create-variant button size=xl
- Open
components/ui/button.tsx - Find the
buttonVariantsCVA configuration - Add to the
sizevariants:
const buttonVariants = cva(
"...",
{
variants: {
variant: { ... },
size: {
default: "h-9 px-4 py-2",
sm: "h-8 rounded-md px-3 text-xs",
lg: "h-10 rounded-md px-8",
icon: "h-9 w-9",
// NEW VARIANT
xl: "h-12 rounded-md px-10 text-lg",
},
},
}
)
- Show usage:
<Button size="xl">Extra Large Button</Button>
Common Variant Types
- variant: Visual style (default, destructive, outline, secondary, ghost, link)
- size: Component size (sm, default, lg, xl)
- state: Interactive state (active, disabled, loading)
- theme: Theme-specific (brand, success, warning, info)
Best Practices
- Keep variant names consistent across components
- Update TypeScript types when adding variants
- Test the variant with all other variant combinations
- Ensure accessibility is maintained
- Document the new variant in comments
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.
- 3d ago First seen · 68 lines · 12 tokens per session scan A 586454c0f501
create-variant is a command published in the GitHub repository Matt-Dionis/claude-code-configs (624 stars, last pushed 1y ago), licensed MIT. It adds 12 tokens to every session and 478 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 commands, from other repositories
prototype-loop
Enter leveraged-prototype focus mode — focus marker plus normal watch/rebuild loop for visual-parity work and batch upstream framework gap-fixes.
review-arch
Review the current branch for code quality, TypeScript, and React/Next.js patterns. Supports whole-branch review or scoped review by path, feature, or base branch.
a11y-audit-react
Identify accessibility violations in React components and provide actionable remediation aligned with WCAG 2.2 Level AA. This is the guided audit workflow that applies the standards defined in the a11y-automation and react-components rules.
react-build
Fix React build failures (Vite, webpack, Next.js, CRA, Parcel, esbuild, Bun) incrementally — JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types. Invokes the react-build-resolver agent for minimal, surgical fixes.
next-upgrade
Structured workflow for upgrading Next.js applications across major versions. Use when migrating a Next.js project from one major version to another (e.g., 13 to 14, 14 to 15, 15 to 16). Covers codemod automation, breaking change detection, incremental migration paths, and post-upgrade validation.
web-design
Design and build a complete website or webapp from a project brief — end-to-end workflow from design to working React/Vite code.