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/virastack/aiWrote 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/rules/virastack/ai/ui)<a href="https://agentmods.dev/rules/virastack/ai/ui"><img src="https://agentmods.dev/badge/rules/virastack/ai/ui/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/rules/virastack/ai/ui"><img src="https://agentmods.dev/badge/rules/virastack/ai/ui.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.00000 | $0.00608 |
| Opus 5.5 | $0.00000 | $0.00243 |
| Sonnet 5.5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
ui 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ui — 89% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI
Components
components/ui: primitives without data or store access.components/shared: reused app components.features/<feature>/components: domain UI.- Add primitives with
{{EXEC_COMMAND}} shadcn@latest add <component>; do not hand-write them. - Find the primitive library first:
styleincomponents.json(base-…orradix-…), elsepackage.json(@base-ui/reactor@radix-ui/*). Never mix them. - Merge classes with
cn()(@/lib/utils), never template strings. - Data-driven UI has loading (a skeleton of the final size), empty and error states.
- Animate with
motion/reactand respect reduced motion.
Tailwind CSS 4
- Theme tokens and the default scale only (
bg-background,p-4). No hex, rgb or arbitrary values likep-[13px]. - v4 class names:
bg-linear-to-rinstead ofbg-gradient-to-r,size-4instead ofw-4 h-4. - Mobile first from 320px; check every breakpoint up to
xl.
Accessibility
- Semantic HTML:
buttonfor actions, links for navigation, oneh1per page, no skipped heading levels. - Every control has a name: visible text, a
<label>, oraria-labelif nothing is visible. - Everything works by keyboard and focus is visible.
- Dialogs and menus use the primitive's focus handling, never a custom focus trap.
- Text contrast meets WCAG AA (4.5:1). Never show state with color alone.
- Meaningful
alttext;alt=""for decorative images.
Bans
onClickondivorspan.- The generic "AI look": indigo or purple defaults, gradients everywhere,
rounded-2xlon everything, identical card grids. Lorem ipsum.
type StatCardProps = { label: string; value: string; className?: string };
export function StatCard({ label, value, className }: StatCardProps) { return ( <section className={cn("rounded-lg border bg-card p-4 md:p-6", className)}> {label} {value} ); }
</example>
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.
- 8d ago First seen · 54 lines · 0 tokens per session scan A 2c5f21c08498
ui is a cursor rule published in the GitHub repository virastack/ai (23 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 608 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-10-22.
Other cursor rules, from other repositories
rtl-right-to-left-i18n-cursorrules-prompt-file
Cursor rules for RTL development with logical CSS properties, Tailwind logical classes, bidirectional text, and automated auditing via rtlify-ai.
qwik-tailwind-cursorrules-prompt-file
Cursor rules for Qwik development with Tailwind CSS integration.
react-chakra-ui-cursorrules-prompt-file
Cursor rules for React development with Chakra UI integration.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.
uizze-ui-finish-gate
Apply the UIZZE design contract and finish gate to frontend work.