modus-select-vs-dropdown-menu-react

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

React guidance for choosing ModusDropdownMenu over ModusSelect because ModusSelect events may not fire consistently.

In plain words
What is it for?
Use it when replacing a select control, handling itemSelect events, storing the selected value in React state, or controlling the menu with refs.
Why use it?
It removes unreliable selection handling, particularly during Chrome DevTools automation and testing.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when replacing a select control, handling itemSelect events, storing the selected value in React state, or controlling the menu with refs.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/julianoczkowski/create-trimble-app/modus-select-vs-dropdown-menu-react
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.

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-select-vs-dropdown-menu-react

README.md
[![agentmods](https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-select-vs-dropdown-menu-react.svg)](https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-select-vs-dropdown-menu-react)
Your own site
<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-select-vs-dropdown-menu-react"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-select-vs-dropdown-menu-react.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 3,055 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.03055
Opus 5 $0.00000 $0.01528
Sonnet 5 $0.00000 $0.00611
Haiku 4.5 $0.00000 $0.00305

Measured 4d ago against content hash 541ecfe91b03, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

modus-select-vs-dropdown-menu-react 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

templates/react/.cursor/rules/modus-select-vs-dropdown-menu-react.mdc · 443 lines

How it starts

The opening of the file, as written. The whole thing — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ModusSelect vs ModusDropdownMenu in React

🚨 CRITICAL: ModusSelect Reliability Issues

Problem: ModusSelect component has unreliable event handling in React applications, especially with Chrome DevTools automation and testing.

Root Cause: ModusSelect events are inconsistent and may not fire reliably in React environments.

Solution: Use ModusDropdownMenu with itemSelect events, which are more reliable and consistent.

Common Anti-Patterns

Using ModusSelect (Unreliable)

// ❌ WRONG: ModusSelect with unreliable events
function UnreliableSelect() {
  const [selectedValue, setSelectedValue] = useState("");

  const options = [
    { label: "Option 1", value: "option1" },
    { label: "Option 2", value: "option2" },
    { label: "Option 3", value: "option3" },
  ];

  const handleInputChange = (event: CustomEvent<InputEvent>) => {
    // ❌ This event may not fire reliably in React
    console.log("Select changed:", event.target.value);
    setSelectedValue(event.target.value);
  };

  return (
    <ModusSelect
      options={options}
      value={selectedValue}
      onInputChange={handleInputChange} // ❌ Unreliable event
      label="Select an option"
    />
  );
}

Direct Event Handling

// ❌ WRONG: Direct event handling
function DirectEventHandling() {
  const options = [
    { label: "Option 1", value: "1" },
    { label: "Option 2", value: "2" },
  ];

  const handleInputChange = (event: CustomEvent<InputEvent>) => {
    // ❌ This may not work consistently in React
    const value = event.target.value;
    console.log("Selected:", value);
  };

  return <ModusSelect options={options} onInputChange={handleInputChange} />;
}

Correct Patterns

Use ModusDropdownMenu (Reliable)

// ✅ CORRECT: ModusDropdownMenu with reliable events
function ReliableDropdown() {
  const [selectedValue, setSelectedValue] = useState("");
  const [isOpen, setIsOpen] = useState(false);
  const dropdownRef = useRef<HTMLModusWcDropdownMenuElement>(null);

  const handleItemSelect = (event: CustomEvent<{ value: string }>) => {
    // ✅ CORRECT: Reliable itemSelect event
    const value = event.detail.value;
    console.log("Item selected:", value);
    setSelectedValue(value);
    setIsOpen(false);
  };

  const toggleDropdown = () => {
    if (dropdownRef.current) {
      dropdownRef.current.menuVisible = !isOpen;
      setIsOpen(!isOpen);
    }
  };

  const menuItems = [
    { label: "Option 1", value: "option1" },
    { label: "Option 2", value: "option2" },
    { label: "Option 3", value: "option3" },
  ];

  return (
    <ModusDropdownMenu
      ref={dropdownRef}
      menuVisible={isOpen}
      onItemSelect={handleItemSelect}
      buttonContent={
        <ModusWcButton onClick={toggleDropdown}>
          {selectedValue || "Select an option"}
        </ModusWcButton>
      }
      menuItems={menuItems}
    />
  );
}

Read the full file on GitHub · 443 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. 4d ago First seen · 443 lines · 0 tokens per session scan A 541ecfe91b03

Subscribe to this mod's changes

modus-select-vs-dropdown-menu-react is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,055 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-09-03.