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-development-workflow-shortgit 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.00383 | $0.00383 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
modus-angular-development-workflow-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 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.
What it actually says
Modus Development Workflow - Short
Essential linting and quality checks for Angular + Vite development.
Key Rules
- Run linting commands during development -
npm run lint:allbefore commits - Fix violations before committing - No violations in committed code
- Check inline styles -
npm run lint:stylesto catch inline style violations - Verify design system colors -
npm run lint:colorsfor color compliance - Validate Modus icons -
npm run lint:iconsfor icon usage - Check border usage -
npm run lint:bordersfor border compliance - Check opacity utilities -
npm run lint:opacityfor opacity compliance
Linting Commands
npm run lint:styles # Check inline styles
npm run lint:colors # Check color usage
npm run lint:icons # Check icon usage
npm run lint:borders # Check border violations
npm run lint:opacity # Check opacity utilities
npm run type-check # TypeScript validation
npm run lint:all # Run all checks
Angular Best Practices
- Use standalone components with signal-based APIs
- Use
input()andoutput()functions, not decorators - Use
ChangeDetectionStrategy.OnPushfor performance - Use
inject()for dependency injection - Use modern control flow (
@if,@for,@switch)
Reference
For detailed workflow guide and quality gates, fetch the full rule: modus-angular-development-workflow
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 · 44 lines · 383 tokens per session scan A 4a69a77d7f12
modus-angular-development-workflow-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It adds 383 tokens to every session, about $0.0019 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
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.