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-master)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-react-master"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-react-master.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.01496 | $0.01496 |
| Opus 5 | $0.00748 | $0.00748 |
| Sonnet 5 | $0.00299 | $0.00299 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
modus-react-master 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modus React Rules - Master Reference
This master rule provides an overview of all available rules and serves as an entry point for understanding the Modus React development patterns.
Rule Structure
This project uses a short/full rule pattern:
- Short Rules (
*-short.mdc): Always applied, concise summaries - Full Rules (
*.mdc): Apply intelligently, detailed patterns
See README.md in this directory for complete rule documentation.
Essential Rules (Always Applied)
These short rules are always included in chat context:
Design System
modus-color-usage-react-short.mdc- Color system usagemodus-icons-react-short.mdc- Icon usage patternsmodus-semantic-html-react-short.mdc- HTML element usageborder-usage-guidelines-short.mdc- Border utilitiesmodus-opacity-utilities-react-short.mdc- Opacity utilitiesmodus-tailwind-usage-react-short.mdc- Tailwind integrationmodus-themes-react-short.mdc- Theme implementation
Component Patterns
modus-button-group-usage-react-short.mdc- Button group patternsmodus-checkbox-value-inversion-react-short.mdc- Checkbox bug handlingmodus-modal-implementation-react-short.mdc- Modal patternsmodus-accordion-state-management-react-short.mdc- Accordion statemodus-select-vs-dropdown-menu-react-short.mdc- Dropdown patternsmodus-navbar-side-navigation-react-short.mdc- Navigation integration
React Integration
modus-react-integration-short.mdc- React + Modus integrationmodus-react-best-practices-short.mdc- React best practicesmodus-react-key-warnings-short.mdc- React key prop patterns
Workflow
development-workflow-react-short.mdc- Linting and quality checkschrome-devtools-testing-react-short.mdc- Browser testingimplementation-guides-react-short.mdc- Feature development guidesmodus-no-emojis-react-short.mdc- Emoji prohibition
Detailed Rules (Apply Intelligently)
For detailed patterns, examples, and advanced techniques, reference these full rules:
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 · 161 lines · 1,496 tokens per session scan A 482f63723054
modus-react-master is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It adds 1,496 tokens to every session, about $0.0075 per session on Opus 5. 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-theming
Theming, dark mode, and color system conventions for the project.
ui
UI/dashboard rules — vanilla JS, no frameworks.
design-ux
Accessibility and design-system conventions for the web dashboard and marketing site.