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/julianoczkowski/create-trimble-appWrote 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/julianoczkowski/create-trimble-app/modus-tailwind-usage-solidjs)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-tailwind-usage-solidjs"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-tailwind-usage-solidjs.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.04831 |
| Opus 5 | $0.00000 | $0.02416 |
| Sonnet 5 | $0.00000 | $0.00966 |
| Haiku 4.5 | $0.00000 | $0.00483 |
Grade A, and why
modus-tailwind-usage-solidjs 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 4d 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
95% identical to modus-tailwind-usage-react — 206 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 — 643 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailwind CSS Usage in SolidJS + Vite
🎨 Tailwind v3 Integration
CRITICAL: This SolidJS + Vite application uses Tailwind CSS v3 (not v4) with Modus Design System integration.
Configuration: Tailwind v3 with design system colors mapped in tailwind.config.js and custom utilities in src/index.css
❌ FORBIDDEN: Generic Tailwind Colors
❌ Never Use Generic Tailwind Color Classes
// ❌ WRONG: Generic Tailwind color classes
class = "bg-blue-500 text-white border-gray-300";
class = "bg-red-400 text-yellow-200 border-green-500";
class = "bg-gray-100 text-black border-purple-300";
class = "bg-indigo-600 text-orange-100 border-pink-400";
❌ Never Use Hardcoded Colors
// ❌ WRONG: Hardcoded colors
class="bg-[#ffffff] text-[#000000] border-[#e5e5e5]"
class="bg-[#3b82f6] text-[#ffffff] border-[#1d4ed8]"
style={{ backgroundColor: "#ffffff", color: "#000000" }}
❌ Never Use Raw Modus Variables
// ❌ WRONG: Raw Modus CSS variables
class="bg-[var(--modus-wc-color-base-page)]"
class="text-[var(--modus-wc-color-base-content)]"
style={{ backgroundColor: "var(--modus-wc-color-base-page)" }}
✅ CORRECT: Design System Colors
✅ Use Design System Tailwind Classes
// ✅ CORRECT: Design system colors
class = "bg-background text-foreground";
class = "bg-card text-card-foreground border border-border";
class = "bg-primary text-primary-foreground hover:bg-primary/90";
class = "bg-secondary text-secondary-foreground hover:bg-secondary/90";
class = "bg-muted text-muted-foreground";
class = "bg-accent text-accent-foreground";
class = "bg-destructive text-destructive-foreground";
class = "bg-warning text-warning-foreground";
class = "bg-success text-success-foreground";
✅ Available Design System Colors
// ✅ CORRECT: All available design system colors
const designSystemColors = {
// Background colors
background: "bg-background",
card: "bg-card",
popover: "bg-popover",
sidebar: "bg-sidebar",
// Text colors
foreground: "text-foreground",
"card-foreground": "text-card-foreground",
"popover-foreground": "text-popover-foreground",
"sidebar-foreground": "text-sidebar-foreground",
// Primary colors
primary: "bg-primary",
"primary-foreground": "text-primary-foreground",
// Secondary colors
secondary: "bg-secondary",
"secondary-foreground": "text-secondary-foreground",
// Muted colors
muted: "bg-muted",
"muted-foreground": "text-muted-foreground",
// Accent colors
accent: "bg-accent",
"accent-foreground": "text-accent-foreground",
// Status colors
destructive: "bg-destructive",
"destructive-foreground": "text-destructive-foreground",
warning: "bg-warning",
"warning-foreground": "text-warning-foreground",
success: "bg-success",
"success-foreground": "text-success-foreground",
// Border colors
border: "border-border",
input: "border-input",
"sidebar-border": "border-sidebar-border",
// Ring colors
ring: "ring-ring",
"sidebar-ring": "ring-sidebar-ring",
// Chart colors
"chart-1": "bg-chart-1",
"chart-2": "bg-chart-2",
"chart-3": "bg-chart-3",
"chart-4": "bg-chart-4",
"chart-5": "bg-chart-5",
// Sidebar colors
sidebar: "bg-sidebar",
"sidebar-foreground": "text-sidebar-foreground",
"sidebar-primary": "bg-sidebar-primary",
"sidebar-primary-foreground": "text-sidebar-primary-foreground",
"sidebar-accent": "bg-sidebar-accent",
"sidebar-accent-foreground": "text-sidebar-accent-foreground",
"sidebar-border": "border-sidebar-border",
"sidebar-ring": "ring-sidebar-ring",
};
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.
- 4d ago First seen · 643 lines · 0 tokens per session scan A 9c218a954520
modus-tailwind-usage-solidjs is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,831 tokens. A static security scan graded it A with 0 findings. It is 95% identical to modus-tailwind-usage-react, differing in 206 lines, and is treated as a copy.
Other cursor rules, from other repositories
hatch3r-design-system-detection
Mandatory detection of existing design tokens, theme primitives, and component library before AI agents author new UI components.
hatch3r-ux-states-and-flows
Four-state surface contract (loading/empty/error/partial), user-flow decomposition before implementation, and microcopy + tone discipline for end-user UIs.
hatch3r-accessibility-standards
Accessibility standards covering WCAG 2.2 AA compliance, keyboard navigation, screen readers, and ARIA patterns.
hatch3r-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
hatch3r-theming
Theming, dark mode, and color system conventions for the project.
design-ux
Accessibility and design-system conventions for the web dashboard and marketing site.