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-select-vs-dropdown-menugit 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-select-vs-dropdown-menu)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-angular-select-vs-dropdown-menu"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-angular-select-vs-dropdown-menu.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00624 |
| Opus 5 | $0.00000 | $0.00312 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
modus-angular-select-vs-dropdown-menu 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 3d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ModusSelect vs ModusDropdownMenu in Angular
CRITICAL: ModusSelect Reliability Issues
Problem: ModusSelect component has unreliable event handling in some scenarios, especially with Chrome DevTools automation and testing.
Solution: Use ModusDropdownMenu with itemSelect events, which are more reliable and consistent.
Correct Pattern: Use ModusDropdownMenu
// CORRECT: ModusDropdownMenu with reliable events
@Component({
template: `
<modus-dropdown-menu
[menuVisible]="isOpen()"
(itemSelect)="handleItemSelect($event)"
(menuVisibleChange)="isOpen.set($event)"
>
<modus-button
slot="trigger"
variant="outlined"
(buttonClick)="toggleDropdown()"
>
{{ selectedLabel() || 'Select an option' }}
<i class="modus-icons ml-2">{{ isOpen() ? 'caret_up' : 'caret_down' }}</i>
</modus-button>
@for (item of menuItems(); track item.value) {
<modus-menu-item
[value]="item.value"
[class.bg-primary-20]="selectedValue() === item.value"
>
{{ item.label }}
</modus-menu-item>
}
</modus-dropdown-menu>
`,
changeDetection: ChangeDetectionStrategy.OnPush,
})
export class ReliableDropdownComponent {
readonly selectedValue = signal<string>('');
readonly isOpen = signal(false);
readonly menuItems = signal([
{ label: 'Option 1', value: 'option1' },
{ label: 'Option 2', value: 'option2' },
{ label: 'Option 3', value: 'option3' },
]);
readonly selectedLabel = computed(() => {
const item = this.menuItems().find(i => i.value === this.selectedValue());
return item?.label ?? '';
});
handleItemSelect(event: CustomEvent<{ value: string }>): void {
const value = event.detail.value;
this.selectedValue.set(value);
this.isOpen.set(false);
}
toggleDropdown(): void {
this.isOpen.update(open => !open);
}
}
Key Takeaways
- Prefer ModusDropdownMenu: Use
ModusDropdownMenufor reliable event handling - Reliable Events:
itemSelectevents are more reliable thaninputChangeevents - Programmatic Control: Use
menuVisibleproperty for programmatic control - Event Handling: Use proper event handling patterns with signals
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.
- 3d ago First seen · 84 lines · 0 tokens per session scan A cf19abf00314
modus-angular-select-vs-dropdown-menu is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 624 tokens. 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.