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-icons-react-short)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-icons-react-short"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-icons-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.00242 | $0.00242 |
| Opus 5 | $0.00121 | $0.00121 |
| Sonnet 5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
modus-icons-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-icons-solidjs-short — 95% identical, 4 lines differ
What it actually says
Modus Icons - Short
Essential icon usage rules for Modus Design System.
REFERENCE: For allowed list of Modus icon names see .cursor/rules/modus-icon-names.mdc
Key Rules
- Use Modus icons exclusively -
<i className="modus-icons">icon-name</i> - Never use other icon libraries - No Font Awesome, Material Icons, Heroicons, etc.
- Use valid icon names only - Check Modus Icons documentation for valid names
- Size with Tailwind classes -
text-sm,text-lg,text-xlfor sizing - Color with design system -
text-primary,text-foreground,text-muted-foreground - Use CDN import - Ensure Modus Icons CDN is loaded
- Test icon rendering - Verify icons display correctly in all themes
Reference
For detailed icon usage patterns, sizing guidelines, and advanced icon techniques, fetch the full rule: modus-icons-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 · 25 lines · 242 tokens per session scan A 1742f1604862
modus-icons-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 242 tokens to every session, about $0.0012 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-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
ant-design
Definitive guidelines for building consistent, performant, and maintainable UIs with Ant Design v6.x, focusing on design tokens, layout, and component usage.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.
815-reactflow-diagrams
Conventions for narrative @xyflow/react canvases: custom nodes and edges, semantic stroke colors, Cloudflare orange shell grouping, readability inside tinted frames, handles, and verification before merge.
frontend-specialist
Senior Frontend Architect who builds maintainable React/Next.js systems with performance-first mindset. Use when working on UI components, styling, state management, responsive design, or frontend architecture. Triggers on keywords like component, react, vue, ui, ux, css, tailwind, responsive. Use with /frontend…
hip-component
You are an expert design system engineer who is well versed in both https://stylexjs.com/ and https://react-spectrum.adobe.com/react-aria/getting-started.html. When implementing components they should follow the same structure as other components in packages/hip-ui/src/components.