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/matteocervelli/llmsWrote 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/matteocervelli/llms/ui-component-create)<a href="https://agentmods.dev/commands/matteocervelli/llms/ui-component-create"><img src="https://agentmods.dev/badge/commands/matteocervelli/llms/ui-component-create/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/commands/matteocervelli/llms/ui-component-create"><img src="https://agentmods.dev/badge/commands/matteocervelli/llms/ui-component-create.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.00015 | $0.02150 |
| Opus 5.5 | $0.00006 | $0.00860 |
| Sonnet 5.5 | $0.00003 | $0.00430 |
| Haiku 4.5 | $0.00002 | $0.00215 |
Grade A, and why
ui-component-create 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 1mo 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create UI Component
Create a production-ready UI component with TypeScript, variants, comprehensive tests, and preview integration.
What it does
- Parses component name and summary from arguments
- Creates component file with TypeScript and variants
- Generates comprehensive test file
- Adds component to preview page
- Runs quality checks (linting, type checking, tests)
- Verifies accessibility compliance
Usage
/ui-component Button "Primary action button with variants"
/ui-component Modal "Dialog component for user interactions"
/ui-component Input "Text input field with validation"
💡 Tip: For safer planning, activate Plan Mode (press Shift+Tab twice) before running this command to review the component structure before creation.
Context
Parse $ARGUMENTS to extract:
- [name]: Component name (converted to PascalCase)
- [summary]: Component purpose/description
Example: /ui-component Card "Display content in a card layout"
- [name] = Card
- [summary] = Display content in a card layout
Component Creation
File Structure
Create in: src/components/ui/[name]/[name].tsx
import { FC } from 'react';
interface [name]Props {
variant?: 'primary' | 'secondary' | 'success' | 'danger' | 'warning';
size?: 'sm' | 'md' | 'lg';
disabled?: boolean;
className?: string;
children?: React.ReactNode;
}
/**
* [name] Component
*
* [summary]
*
* @example
* ```tsx
* <[name] variant="primary" size="md">
* Content here
* </[name]>
* ```
*/
export const [name]: FC<[name]Props> = ({
variant = 'primary',
size = 'md',
disabled = false,
className,
children,
}) => {
// Implementation
return (
<div
className={cn(baseStyles, variantStyles[variant], sizeStyles[size], className)}
aria-disabled={disabled}
>
{children}
</div>
);
};
Required Variants
Use theme colors from @src/app/globals.css:
- primary - Main brand color (primary action)
- secondary - Secondary brand color (less emphasis)
- success - Success/confirmation actions (green)
- danger - Destructive/error actions (red)
- warning - Caution/warning states (orange)
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.
- 1mo ago First seen · 358 lines · 15 tokens per session scan A d6540de4b637
ui-component-create is a command published in the GitHub repository matteocervelli/llms (25 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 2,150 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
implement-from-plan
You are in implementation-only mode.
story-and-test
For the component(s) in scope.
add-tests
Add comprehensive tests for React components or functions using React Testing Library and Jest.
component-scaffold
You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, styles, and documentation following modern best practices.
hooks
Create or optimize React hooks for $ARGUMENTS following project conventions.
state-management
Implement state management solution for $ARGUMENTS following project conventions.