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-short)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-tailwind-usage-solidjs-short"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-tailwind-usage-solidjs-short.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.00246 | $0.00246 |
| Opus 5 | $0.00123 | $0.00123 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
modus-tailwind-usage-solidjs-short 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
100% identical to modus-tailwind-usage-react-short — 2 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.
What it actually says
Modus Tailwind Usage - Short
Tailwind CSS v3 with Modus Design System integration.
Key Rules
- Tailwind v3 with design system - Use Tailwind v3 with Modus Design System integration
- No generic Tailwind colors - Never use
bg-blue-500,text-gray-600, etc. - Use design system colors -
bg-background,text-foreground,bg-primary, etc. - Custom utilities for borders - Use
border-default,border-success,border-warning, etc. - Elevation utilities - Use
elevation-1,elevation-2,elevation-3for shadows - Proper CSS import order - Modus CSS before Tailwind CSS
- Test in all themes - Ensure Tailwind classes work in all 6 themes
Reference
For detailed Tailwind integration, custom utilities, and advanced styling patterns, fetch the full rule: modus-tailwind-usage-solidjs
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 · 24 lines · 246 tokens per session scan A ea30db8356d6
modus-tailwind-usage-solidjs-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It adds 246 tokens to every session, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to modus-tailwind-usage-react-short, differing in 2 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.