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-forms-validation-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.00381 | $0.00381 |
| Opus 5 | $0.00191 | $0.00191 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
modus-angular-forms-validation-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 Forms Validation - Short
Essential patterns for forms and validation with Modus Web Components.
Key Rules
- Always use Reactive Forms - Don't use template-driven forms
- Track touched state manually - Modus components don't integrate with Angular form state
- Use computed signals for feedback - Reactive, efficient validation
- Check touched state before showing errors - Better UX
- Handle both inputChange and inputBlur - Complete interaction tracking
- Extract event.detail - Correct event handling pattern
Manual Touch Tracking
readonly touchedFields = signal<Set<string>>(new Set());
handleFieldChange(event: InputEvent, fieldName: string): void {
const target = event.target as HTMLInputElement;
this.form.controls[fieldName].setValue(target.value);
this.markFieldTouched(fieldName);
}
private markFieldTouched(fieldName: string): void {
this.touchedFields.update((fields) => {
const newFields = new Set(fields);
newFields.add(fieldName);
return newFields;
});
}
Validation Feedback
readonly emailFeedback = computed<IInputFeedbackProp | undefined>(() => {
const control = this.form.controls.email;
const isTouched = this.touchedFields().has('email');
if (!isTouched || !control.errors) return undefined;
if (control.errors['required']) {
return { level: 'error', message: 'Email is required.' };
}
return undefined;
});
Reference
For detailed form patterns and validation strategies, fetch the full rule: modus-angular-forms-validation
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 · 57 lines · 381 tokens per session scan A 15bf3ca4c582
modus-angular-forms-validation-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It adds 381 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
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.