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-opacity-utilities-react)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-opacity-utilities-react"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-opacity-utilities-react.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.01753 |
| Opus 5 | $0.00000 | $0.00877 |
| Sonnet 5 | $0.00000 | $0.00351 |
| Haiku 4.5 | $0.00000 | $0.00175 |
Grade A, and why
modus-opacity-utilities-react 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- modus-opacity-utilities-solidjs — 92% identical, 66 lines differ
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modus Opacity Utilities - React
Essential opacity utilities for Modus Design System colors in React + Vite.
Key Rules
- 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% -
text-foreground-80,bg-primary-80,border-destructive-80 - 60% -
text-foreground-60,bg-primary-60,border-destructive-60 - 40% -
text-foreground-40,bg-primary-40,border-destructive-40 - 20% -
text-foreground-20,bg-primary-20,border-destructive-20
Available Colors
- foreground -
text-foreground-80,bg-foreground-80,border-foreground-80 - muted-foreground -
text-muted-foreground-80,bg-muted-foreground-80 - primary -
text-primary-80,bg-primary-80,border-primary-80 - secondary -
text-secondary-80,bg-secondary-80 - destructive -
text-destructive-80,bg-destructive-80,border-destructive-80 - warning -
text-warning-80,bg-warning-80,border-warning-80 - success -
text-success-80,bg-success-80,border-success-80
Usage Examples
Text Opacity
// ❌ This doesn't work with CSS variables
<div className="text-foreground/80">Text with 80% opacity</div>
// ✅ Use custom opacity utilities
<div className="text-foreground-80">Text with 80% opacity</div>
<div className="text-primary-60">Primary text with 60% opacity</div>
<div className="text-muted-foreground-40">Muted text with 40% opacity</div>
Background Opacity
// ✅ Background opacity utilities
<div className="bg-primary-80">Primary background with 80% opacity</div>
<div className="bg-destructive-60">Destructive background with 60% opacity</div>
<div className="bg-warning-40">Warning background with 40% opacity</div>
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 · 209 lines · 0 tokens per session scan A ac5200adff62
modus-opacity-utilities-react 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 1,753 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-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.