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 rules/muzaffar640/commitpress/ui-componentsgit clone --depth 1 https://github.com/muzaffar640/commitpressWhat 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.00000 | $0.01221 |
| Opus 5 | $0.00000 | $0.00611 |
| Sonnet 5 | $0.00000 | $0.00244 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
ui-components 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: globs: alwaysApply: true
UI Components
Component Organization
- Basic UI components should be placed in src/components/ui/
- Blog-specific components should be placed in src/components/Blog/
- MDX components should be placed in src/components/MDX/
- Layout components should be placed in src/components/
UI Component Guidelines
- Create small, reusable components
- Use TypeScript interfaces for props
- Follow a consistent naming convention
- Implement proper accessibility attributes
- Use Tailwind CSS for styling
- Follow shadcn/ui patterns when possible
Component Examples
Button Component
// Basic button component example
interface ButtonProps {
variant?: 'primary' | 'secondary' | 'outline';
size?: 'sm' | 'md' | 'lg';
children: React.ReactNode;
onClick?: () => void;
disabled?: boolean;
className?: string;
}
const Button = ({
variant = 'primary',
size = 'md',
children,
onClick,
disabled = false,
className = ''
}: ButtonProps) => {
const baseClasses = 'inline-flex items-center justify-center rounded-md font-medium transition-colors focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring disabled:pointer-events-none disabled:opacity-50';
const variantClasses = {
primary: 'bg-primary text-primary-foreground hover:bg-primary/90',
secondary: 'bg-secondary text-secondary-foreground hover:bg-secondary/80',
outline: 'border border-input bg-background hover:bg-accent hover:text-accent-foreground'
};
const sizeClasses = {
sm: 'h-9 px-3 text-sm',
md: 'h-10 px-4 py-2',
lg: 'h-11 px-8 text-lg'
};
return (
<button
onClick={onClick}
disabled={disabled}
className={`${baseClasses} ${variantClasses[variant]} ${sizeClasses[size]} ${className}`}
>
{children}
</button>
);
};
Card Component
// Basic card component example
interface CardProps {
title?: string;
description?: string;
children: React.ReactNode;
className?: string;
}
const Card = ({ title, description, children, className = '' }: CardProps) => {
return (
<div className={`rounded-lg border bg-card text-card-foreground shadow-sm ${className}`}>
<div className="p-6">
{title && <h3 className="text-2xl font-semibold leading-none tracking-tight mb-2">{title}</h3>}
{description && <p className="text-sm text-muted-foreground mb-4">{description}</p>}
{children}
</div>
</div>
);
};
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 · 185 lines · 0 tokens per session scan A 7f85874d3b8d
ui-components is a cursor rule published in the GitHub repository muzaffar640/commitpress (7 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,221 tokens. 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.
Other cursor rules, from other repositories
project-structure
Overall project structure & standards.
utilities
Project utilities & helper functions for use across the project.
ui-components
Cursor rule "ui-components" from FluroAsh/nextjs-mdx-portfolio, covering ui components and styling, component libraries, shadcn/ui, custom components and styling approach.
testing
Testing standards & Practices.
accessibility
Accessibility standards.
avoid-nested-code-blocks
See README.md for more details. description: globs: alwaysApply: false.