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/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/louisbrulenaudet/monorepo-template/tailwind"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/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.01863 |
| Opus 5.5 | $0.00000 | $0.00745 |
| Sonnet 5.5 | $0.00000 | $0.00373 |
| Haiku 4.5 | $0.00000 | $0.00186 |
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 15d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailwind CSS v4
CSS-first v4: there is no tailwind.config.js / postcss.config.js. Motion and interaction depth: skill ui-ux-design-best-practices. Lint configuration: lint-config.mdc.
Engine and source detection
- Single entry
@import "tailwindcss" source(none);insrc/index.css(canonical:apps/front-app/src/index.css), built by@tailwindcss/vitewith Lightning CSS built in - no Autoprefixer/PostCSS step. Plugin order: vite-config.mdc. source(none)turns off v4's automatic detection, which starts from the build's working directory and would also scantests/,README.md, andAGENTS.md(prose there can emit stray utilities).@source "../index.html"+@source "./**/*.{ts,tsx}"are then the complete allowlist, so detection stays cwd-independent.- Register a workspace package only when it ships Tailwind classes this app renders, pointing at its real source (
@source "../../../packages/<pkg>/src";), not thenode_modulessymlink.@repo/dtos-common/@repo/enums-commonare class-free: never add them. @source not "<path>";excludes a large non-Tailwind directory.@source inline("...")safelists classes that never appear as literals - a last resort; prefer static strings.
Tokens: @theme vs :root
@themeonly for a value that must generate a utility or variant, i.e. one in a Tailwind namespace (--color-*,--spacing-*,--font-*,--radius-*,--shadow-*,--ease-*,--animate-*,--breakpoint-*).@themeis top-level only (no nesting under selectors or media). Every other custom property stays in plain:root(e.g.--health-glow-color).@keyframesfor an--animate-*token nest inside@theme, so they travel with the token.@theme inlinewhen a token's value is itself avar(...)(semantic theming), so the utility resolves per scope instead of baking in one value.- Font stacks are tokens (
@theme { --font-sans: ... }, which preflight applies tohtml), neverfont-familyon:root. - The first
@themeresets the default palette (--color-*: initial): only the semantic@theme inlinecolors generate utilities, sono-unknown-classesrejectstext-white,bg-red-500, and every other single-theme palette class. A new tint starts as a semantic token.
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.
- 15d ago Changed · +8 lines 2dcd37eb466e
- 23d ago Changed · -23 lines 51c5c641b743
- 25d ago Changed · +2 lines 03696742d102
- 27d ago Changed 9e25d2635e8c
- 1mo 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 today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,863 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.
react-chakra-ui-cursorrules-prompt-file
Cursor rules for React development with Chakra UI 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.
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.
uizze-ui-finish-gate
Apply the UIZZE design contract and finish gate to frontend work.
frontend-theme-guidelines
Frontend theme-system rules for NekroAgent, covering the theme architecture, core file structure, design principles, and usage guidance. A theme system controls shared visual choices such as colors, typography, and layouts.