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-react-essentials)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-react-essentials"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-react-essentials.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.02604 |
| Opus 5 | $0.00000 | $0.01302 |
| Sonnet 5 | $0.00000 | $0.00521 |
| Haiku 4.5 | $0.00000 | $0.00260 |
Grade A, and why
modus-react-essentials 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.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modus React Essentials
Comprehensive essential rules for React + Vite development with Modus Design System.
Design System Integration
Color Usage
- Use design system colors only -
bg-background,text-foreground,bg-primary, etc. - Never use generic Tailwind colors - No
bg-blue-500,text-gray-600, etc. - Never use hardcoded values - No hex colors, RGB values, or CSS variables
- Use semantic color names -
bg-destructive,text-warning,bg-success - Follow color hierarchy - Background → Card → Primary → Secondary → Muted → Accent
- Use hover states -
hover:bg-primary/90for interactive elements - Test in all themes - Ensure colors work in light and dark modes
Opacity Usage
- Use custom opacity utilities, not Tailwind /80 syntax -
text-foreground-80nottext-foreground/80 - CSS variables don't work with Tailwind opacity modifiers - Tailwind needs actual color values
- Use color-mix() for opacity variants - Modern CSS function for proper opacity calculation
- All utilities defined in index.css - No Tailwind config changes needed
- Respects theme switching - Works in all 6 Modus themes
- Use semantic color names -
foreground,primary,destructive, etc. - Available opacity levels -
80,60,40,20(e.g.,text-foreground-80,bg-primary-60) - Available utilities -
text-*,bg-*,border-*with opacity variants
Border Usage
- Use design system border utilities only -
border-default,border-success,border-warning,border-destructive,border-primary - Never use Tailwind color classes in borders - No
border-blue-500,border-gray-300, etc. - Use
border-thickfor emphasis - For important borders and separators - Use directional borders -
border-t,border-b,border-l,border-rwith design system colors - No inline styles for borders - Use Tailwind classes exclusively
- Context-specific usage - Cards use
border-default, alerts use semantic colors, forms useborder-input
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 · 210 lines · 0 tokens per session scan A b9286d3e5404
modus-react-essentials 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 2,604 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-09-03.
Other cursor rules, from other repositories
hatch3r-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and 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.
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
chakra-ui---responsive-design
Guidance for making Chakra UI layouts adapt to different screen sizes. It uses responsive style values, breakpoints, layout components, and conditional display rules for phones, tablets, and desktops.