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/ofershap/shadcn-best-practicesWrote 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/ofershap/shadcn-best-practices/best-practices)<a href="https://agentmods.dev/rules/ofershap/shadcn-best-practices/best-practices"><img src="https://agentmods.dev/badge/rules/ofershap/shadcn-best-practices/best-practices/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/ofershap/shadcn-best-practices/best-practices"><img src="https://agentmods.dev/badge/rules/ofershap/shadcn-best-practices/best-practices.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.00147 | $0.00147 |
| Opus 5.5 | $0.00059 | $0.00059 |
| Sonnet 5.5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
best-practices 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 2mo 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
- shadcn/ui components live in your project at @/components/ui/ - never import from @shadcn/ui or any external package
- Use cn() utility from @/lib/utils for merging Tailwind classes - never use template literals for conditional classes
- Use React Hook Form + Zod for all forms with shadcn Form components - never use uncontrolled forms or manual validation
- Use CSS variables for theming - never hardcode colors in components
- Use cva (class-variance-authority) for component variants - never use complex conditional class logic
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.
- 2mo ago First seen · 11 lines · 147 tokens per session scan A 2780d34a836b
best-practices is a cursor rule published in the GitHub repository ofershap/shadcn-best-practices (0 stars, last pushed 8mo ago), licensed MIT. It adds 147 tokens to every session, about $0.0006 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-08-31.
Other cursor rules, from other repositories
react-rendering-performance
React rendering and DOM performance patterns for animations, SVG optimization, CSS content-visibility, conditional rendering, and useTransition loading states. Use when working with animations, SVG elements, long lists, show/hide toggles, or loading state management.
best-practices
Tailwind CSS Best Practices - enforces v4 syntax and CSS-first config when working with Tailwind code.
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.
custom-component
Guide for creating React components using the useProps pattern with Mantine for centralized theme-based styling. Apply when creating or modifying components that need theme integration.