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.
npx agentmods add rules/julianoczkowski/create-trimble-app/modus-angular-essentialsgit clone --depth 1 https://github.com/julianoczkowski/create-trimble-appWhat 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 | $0.02704 | $0.02704 |
| Opus 5 | $0.01352 | $0.01352 |
| Sonnet 5 | $0.00541 | $0.00541 |
| Haiku 4.5 | $0.00270 | $0.00270 |
Grade A, and why
modus-angular-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 2d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modus Angular Essentials
Comprehensive essential rules for Angular + 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 directly
- Use semantic color names -
bg-destructive,text-warning,bg-success - Follow color hierarchy - Background > Card > Primary > Secondary > Muted
- 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
- Available opacity levels -
80,60,40,20(e.g.,text-foreground-80,bg-primary-60) - Available utilities -
text-*,bg-*,border-*with opacity variants - All utilities defined in styles.css - No Tailwind config changes needed
- Respects theme switching - Works in all 6 Modus themes
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
Icons
- Use Modus icons exclusively -
<i class="modus-icons">icon-name</i>or<modus-icon name="icon-name" /> - 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-foreground-60 - Validate icon names - Run
npm run lint:icon-namesto verify
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.
- 2d ago First seen · 273 lines · 2,704 tokens per session scan A 71895702f4d6
modus-angular-essentials is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It adds 2,704 tokens to every session, about $0.0135 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-08-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.