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/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/tailwind)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/tailwind"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/tailwind.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.1 | $0.00000 | $0.02195 |
| Opus 5 | $0.00000 | $0.01097 |
| Sonnet 5 | $0.00000 | $0.00439 |
| Haiku 4.5 | $0.00000 | $0.00219 |
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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailwind CSS v4 Rules
Styling for the React SPAs. Tailwind v4, CSS-first (no tailwind.config.js). Component/hook authoring is in react.mdc; Vite plugin wiring in vite-config.mdc; cross-cutting layout in frontend-architecture.mdc. Motion/interaction depth → ui-ux-design-best-practices skill.
Engine & entry
- Single entry:
@import "tailwindcss";insrc/index.css(canonical:apps/front-app/src/index.css). There is notailwind.config.js/postcss.config.js- v4 configures in CSS. - The build runs through
@tailwindcss/vite(Lightning CSS is built in - no separate Autoprefixer/PostCSS step). Plugin order lives in vite-config.mdc:tailwindcss()afterreact()/babel, beforecloudflare(). - Docs: https://tailwindcss.com/docs/installation/using-vite
Source detection (@source)
- v4 detects templates automatically, scanning from the build's working directory (per-app here, so
apps/front-app/**) and skipping.gitignore,node_modules, binaries, CSS, and lockfiles. The current@source "../index.html"+@source "./**/*.{ts,tsx}"are a defensive restatement of that default - keep them so detection stays cwd-independent. - Register a workspace package only when it ships Tailwind classes this app renders. Point at the real source (
@source "../../../packages/<pkg>/src";), not thenode_modulessymlink.@repo/dtos-common/@repo/enums-commonare class-free - do not add sources for them. @source not "<path>";excludes a large non-Tailwind directory from scanning.@source inline("...")safelists classes that never appear as literals - a last resort; prefer static strings (below).- Docs: https://tailwindcss.com/docs/detecting-classes-in-source-files
Design tokens: @theme vs :root
- Put a value in
@themeonly when it must generate a utility/variant - i.e. it uses a Tailwind namespace (--color-*,--spacing-*,--font-*,--radius-*,--shadow-*,--ease-*,--animate-*,--breakpoint-*).@themeis top-level only (no nesting under selectors/media). - Every other custom property stays in plain
:root(e.g.--health-glow-color,--health-shake-distance- not a namespace, correctly outside@theme). - Keyframes for an
--animate-*token: nest the@keyframesinside@themeso they travel with the token (idiomatic v4). Top-level keyframes also emit correctly but drift from their token. - Use
@theme inlinewhen a token's value is itself avar(...)(semantic theming, below) so the utility resolves per-scope instead of baking in one value. - Docs: https://tailwindcss.com/docs/theme , https://tailwindcss.com/docs/colors
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.
- 7d ago First seen · 75 lines · 0 tokens per session scan A 2e8d6fd06d85
tailwind is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,195 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-30.
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.
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and Tailwind CSS integration.
html-tailwind-css-javascript-cursorrules-prompt-fi
Cursor rules for HTML development with Tailwind CSS and JavaScript integration.
qwik-tailwind-cursorrules-prompt-file
Cursor rules for Qwik development with Tailwind CSS integration.
react-components-creation-cursorrules-prompt-file
Cursor rules for React component creation and development.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.