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/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/tailwind)<a href="https://agentmods.dev/rules/kensaurus/cursor-kenji/tailwind"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/tailwind/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/kensaurus/cursor-kenji/tailwind"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/tailwind.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.00429 |
| Opus 5.5 | $0.00000 | $0.00172 |
| Sonnet 5.5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
tailwind 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.
What it actually says
Tailwind & Styling Conventions
Performance (LCP images, INP, bfcache) → web-performance.mdc.
Design Tokens
- Use CSS variables from
globals.css(e.g.,hsl(var(--primary))) - Use semantic color names:
bg-primary,text-muted-foreground,border-input - Never hardcode hex/rgb values — always use tokens
- Spacing follows 4px/8px grid system
Class Composition
// Use cn() for conditional classes
className={cn(
"base-classes",
variant === "active" && "active-classes",
className // always spread incoming className last
)}
Responsive
- Mobile-first: base styles are mobile,
sm:md:lg:for larger - Breakpoints:
sm:640pxmd:768pxlg:1024pxxl:1280px - Touch targets: minimum 44px height for interactive elements on mobile
Dark Mode
- Use
dark:variant for dark mode overrides - Or use CSS variables that automatically switch (preferred)
- Test all UI in both light and dark modes
Animation
- Use Tailwind animation utilities when possible
- For complex animations, use Framer Motion
- Respect
prefers-reduced-motion:motion-safe:/motion-reduce: - Keep transitions under 300ms for interactions
- Only animate
transformandopacity(GPU-accelerated)
Keep styles in the system
- Styling lives in Tailwind classes, not
style={{}} - Fix specificity at its source;
!importanthides the conflict - Arbitrary values (
w-[347px]) only for a true one-off; anything reused becomes a token - Extend an existing component's variants rather than re-declaring its classes elsewhere
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 Changed db7eff7cfa7b
- 1mo ago First seen · 49 lines · 0 tokens per session scan A 259776293265
tailwind is a cursor rule published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 429 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-09-03.
Other cursor rules, from other repositories
design-systems
Design system mechanics: tokens, shadcn/ui, Tailwind v4, composition, theming. Load for UI implementation — aesthetics and anti-slop live in the anti-slop-design skill.
accessibility
Accessibility (a11y) rules for frontend components. Apply when editing UI or markup.
shadcn-ui
Cursor rule "shadcn-ui" from nedcodes-ok/cursorrules-collection, covering shadcn/ui rules, component usage, styling, forms and dialog/sheet/modal patterns.
180-creative-process-structure
description: WHEN approaching design-intensive tasks APPLY structured creative processes globs: ["/.md", "/.mdc"] alwaysApply: true.
200-quality-verification-procedures
description: WHEN verifying design quality APPLY systematic procedures for validation globs: ["/.md", "/.mdc"] alwaysApply: true.
210-artifact-management-system
description: WHEN managing design artifacts APPLY structured processes for organization and preservation globs: ["/.md", "/.mdc"] alwaysApply: true.