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-angular-development-workflow)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-angular-development-workflow"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-angular-development-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-angular-development-workflow"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-angular-development-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01032 |
| Opus 5.5 | $0.00000 | $0.00413 |
| Sonnet 5.5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade C, and why
modus-angular-development-workflow 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 1mo 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: Design system border utilities --> How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Workflow & Quality Assurance for Angular + Vite
MANDATORY: Always Run Linting Commands During Development
CRITICAL: Before making any code changes, always run these linting commands to ensure design system compliance:
# Check for inline styles that should use Tailwind classes
npm run lint:styles
# Check for non-Modus colors (hex, RGB, Tailwind colors)
npm run lint:colors
# Check for non-Modus icons (Font Awesome, Material Icons, etc.)
npm run lint:icons
# Check for border violations (Tailwind color classes in borders)
npm run lint:borders
# Check for opacity violations (using /80 syntax instead of custom utilities)
npm run lint:opacity
# Validate Modus icon names
npm run lint:icon-names
# Run TypeScript type checking
npm run type-check
# Run all linting checks at once
npm run lint:all
Pre-Development Checklist
Before starting any new feature or component:
-
Run Design System Lints:
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 -
Verify Theme Compatibility:
- Test with all 6 Modus themes (classic/modern, light/dark, connect themes)
- Ensure components work in both light and dark modes
-
Check Component Architecture:
- Use single configurable components (not multiple specific ones)
- Follow Modus Web Components wrapper patterns
- Use signals for state management
Common Violations to Watch For
Inline Styles (lint:styles):
// VIOLATION: Inline styles
template: `<div style="background-color: var(--modus-wc-color-base-page)">`;
template: `<div [style.margin-right.px]="8">`;
// CORRECT: Tailwind classes
template: `<div class="bg-background mr-2 text-foreground">`;
Color Usage (lint:colors):
// VIOLATION: Non-Modus colors
template: `<div style="background-color: #ffffff">`;
template: `<div class="bg-blue-500 text-red-400">`;
// CORRECT: Modus design system colors
template: `<div class="bg-background text-foreground">`;
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.
- 1mo ago First seen · 146 lines · 0 tokens per session scan C df456bbc8031
modus-angular-development-workflow is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,032 tokens. 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
graphql
GraphQL: schema design, resolvers, performance.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.