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-design-systemgit 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.02604 | $0.02604 |
| Opus 5 | $0.01302 | $0.01302 |
| Sonnet 5 | $0.00521 | $0.00521 |
| Haiku 4.5 | $0.00260 | $0.00260 |
Grade C, and why
modus-angular-design-system scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- ✅ CORRECT: Use Tailwind classes with design system colors --> How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Design System - Tailwind v4 with Modus
Design System Overview
This Angular application uses a 9-color design system that enforces semantic color usage through Tailwind classes. Direct usage of --modus-wc-color-* variables is prohibited - only use the 9 semantic colors through Tailwind utilities.
Color System
9 Core Colors
The design system consists of 9 core colors, each with semantic names that map to Modus CDN variables:
| Semantic Name | Modus Variable | Usage |
|---|---|---|
background |
--modus-wc-color-base-page |
Page background |
foreground |
--modus-wc-color-base-content |
Primary text |
card |
--modus-wc-color-base-100 |
Card backgrounds |
muted |
--modus-wc-color-base-200 |
Subtle backgrounds, borders |
secondary |
--modus-wc-color-base-300 |
Secondary UI elements |
primary |
--modus-wc-color-info |
Primary actions, info |
success |
--modus-wc-color-success |
Success states |
warning |
--modus-wc-color-warning |
Warning states |
destructive |
--modus-wc-color-error |
Error/destructive states |
Color Variables in src/styles.css
The 9 semantic colors are mapped to Modus variables in the @theme block:
@theme {
/* 9-Color Design System */
--color-background: var(--modus-wc-color-base-page);
--color-foreground: var(--modus-wc-color-base-content);
--color-card: var(--modus-wc-color-base-100);
--color-card-foreground: var(--modus-wc-color-base-content);
--color-muted: var(--modus-wc-color-base-200);
--color-muted-foreground: var(--modus-wc-color-base-content);
--color-secondary: var(--modus-wc-color-base-300);
--color-secondary-foreground: var(--modus-wc-color-base-content);
--color-primary: var(--modus-wc-color-info);
--color-primary-foreground: var(--modus-wc-color-base-page);
--color-success: var(--modus-wc-color-success);
--color-success-foreground: var(--modus-wc-color-base-page);
--color-warning: var(--modus-wc-color-warning);
--color-warning-foreground: var(--modus-wc-color-base-content);
--color-destructive: var(--modus-wc-color-error);
--color-destructive-foreground: var(--modus-wc-color-base-page);
--color-border: var(--modus-wc-color-base-200);
--color-ring: var(--modus-wc-color-info);
}
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 · 274 lines · 2,604 tokens per session scan C f00828c3a13d
modus-angular-design-system is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It adds 2,604 tokens to every session, about $0.0130 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). 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
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
z-index
Z-index layering conventions for consistent stacking.
design
Rule of thumb: If you can do it with transition- or animate- + data attributes, do not use Motion.