modus-angular-select-vs-dropdown-menu

modus-angular-select-vs-dropdown-menu is a cursor rule for Cursor from julianoczkowski/create-trimble-app. It costs 0 tokens per session (624 once invoked), scanned A, original, MIT.

A comparison rule for choosing between ModusSelect and ModusDropdownMenu in Angular. It recommends ModusDropdownMenu when reliable selection events are important, especially in Chrome DevTools automation and tests.

In plain words
What is it for?
Use it when implementing an Angular menu that lets users choose an option, particularly when the interaction must work reliably in automated tests.
Why use it?
It addresses event-handling problems reported for ModusSelect in some scenarios. The alternative provides a more consistent item-selection event pattern.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/julianoczkowski/create-trimble-app/modus-angular-select-vs-dropdown-menu
Clone the repo
git clone --depth 1 https://github.com/julianoczkowski/create-trimble-app

Made for: Cursor.

Wrote 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.

agentmods badge for modus-angular-select-vs-dropdown-menu

README.md
[![agentmods](https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-angular-select-vs-dropdown-menu.svg)](https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-angular-select-vs-dropdown-menu)
Your own site
<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>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 624 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash cf19abf00314, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

templates/angular/.cursor/rules/modus-angular-select-vs-dropdown-menu.mdc · 84 lines

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

  1. Prefer ModusDropdownMenu: Use ModusDropdownMenu for reliable event handling
  2. Reliable Events: itemSelect events are more reliable than inputChange events
  3. Programmatic Control: Use menuVisible property for programmatic control
  4. Event Handling: Use proper event handling patterns with signals

Read the full file on GitHub · 84 lines

Changes

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.

  1. 3d ago First seen · 84 lines · 0 tokens per session scan A cf19abf00314

Subscribe to this mod's changes

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.