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-semantic-html-react-short)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-semantic-html-react-short"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-semantic-html-react-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.00216 | $0.00216 |
| Opus 5 | $0.00108 | $0.00108 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
modus-semantic-html-react-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- modus-semantic-html-solidjs-short — 95% identical, 2 lines differ
What it actually says
Modus Semantic HTML - Short
Use div elements exclusively to avoid Tailwind CSS conflicts.
Key Rules
- Use div elements only - All content must use
<div>elements - No semantic HTML elements - Never use
h1,p,section,header,footer,nav,main,aside,article,span - Use Tailwind classes for styling - Apply typography and layout with Tailwind classes
- Icon exception - Only
<i>elements allowed for Modus icons - Consistent structure - Maintain consistent div-based component structure
- Accessibility with divs - Ensure proper accessibility with div elements
- Test rendering - Verify components render correctly in all themes
Reference
For detailed HTML patterns, accessibility guidelines, and advanced div usage, fetch the full rule: modus-semantic-html-react
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 · 216 tokens per session scan A 68b5db9d8653
modus-semantic-html-react-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It adds 216 tokens to every session, about $0.0011 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.