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/travishorn/cursor-rules-sveltekit/tailwind-css-4git clone --depth 1 https://github.com/travishorn/cursor-rules-sveltekitWrote 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/travishorn/cursor-rules-sveltekit/tailwind-css-4)<a href="https://agentmods.dev/rules/travishorn/cursor-rules-sveltekit/tailwind-css-4"><img src="https://agentmods.dev/badge/rules/travishorn/cursor-rules-sveltekit/tailwind-css-4.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02221 |
| Opus 5 | $0.00000 | $0.01111 |
| Sonnet 5 | $0.00000 | $0.00444 |
| Haiku 4.5 | $0.00000 | $0.00222 |
Grade A, and why
tailwind-css-4 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 3d 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.
This is a copy
88% identical to tailwindcss — 77 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailwind CSS 4
This project uses the newer Tailwind CSS 4 instead of the older, but more common Tailwind CSS 3.
Core Changes
-
CSS-first configuration: Configuration is now done in CSS instead of JavaScript
- Use
@themedirective in CSS instead oftailwind.config.js - Example:
@import "tailwindcss"; @theme { --font-display: "Satoshi", "sans-serif"; --breakpoint-3xl: 1920px; --color-avocado-500: oklch(0.84 0.18 117.33); --ease-fluid: cubic-bezier(0.3, 0, 0, 1); }
- Use
-
Legacy
tailwind.config.jsfiles can still be imported using the@configdirective:@import "tailwindcss"; @config "../../tailwind.config.js"; -
CSS import syntax: Use
@import "tailwindcss"instead of@tailwinddirectives- Old:
@tailwind base; @tailwind components; @tailwind utilities; - New:
@import "tailwindcss";
- Old:
-
Package changes:
- PostCSS plugin is now
@tailwindcss/postcss(nottailwindcss) - CLI is now
@tailwindcss/cli - Vite plugin is
@tailwindcss/vite - No need for
postcss-importorautoprefixeranymore
- PostCSS plugin is now
-
Native CSS cascade layers: Uses real CSS
@layerinstead of Tailwind's custom implementation
Theme Configuration
- CSS theme variables: All design tokens are available as CSS variables
- Namespace format:
--category-name(e.g.,--color-blue-500,--font-sans) - Access in CSS:
var(--color-blue-500) - Available namespaces:
--color-*: Color utilities likebg-red-500andtext-sky-300--font-*: Font family utilities likefont-sans--text-*: Font size utilities liketext-xl--font-weight-*: Font weight utilities likefont-bold--tracking-*: Letter spacing utilities liketracking-wide--leading-*: Line height utilities likeleading-tight--breakpoint-*: Responsive breakpoint variants likesm:*--container-*: Container query variants like@sm:*and size utilities likemax-w-md--spacing-*: Spacing and sizing utilities likepx-4andmax-h-16--radius-*: Border radius utilities likerounded-sm--shadow-*: Box shadow utilities likeshadow-md--inset-shadow-*: Inset box shadow utilities likeinset-shadow-xs--drop-shadow-*: Drop shadow filter utilities likedrop-shadow-md--blur-*: Blur filter utilities likeblur-md--perspective-*: Perspective utilities likeperspective-near--aspect-*: Aspect ratio utilities likeaspect-video--ease-*: Transition timing function utilities likeease-out--animate-*: Animation utilities likeanimate-spin
- Namespace format:
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.
- 3d ago First seen · 216 lines · 0 tokens per session scan A 9eb2b34a21b4
tailwind-css-4 is a cursor rule published in the GitHub repository travishorn/cursor-rules-sveltekit (9 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,221 tokens. A static security scan graded it A with 0 findings. It is 88% identical to tailwindcss, differing in 77 lines, and is treated as a copy.
Other cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
frontend
Demo Shop frontend guidance.
clean-dom
HTML semantic elements, DOM structure, responsive images, forms, CSS, and Tailwind best practices with accessibility a11y.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.