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-select-vs-dropdown-menu-react)<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>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.03055 |
| Opus 5 | $0.00000 | $0.01528 |
| Sonnet 5 | $0.00000 | $0.00611 |
| Haiku 4.5 | $0.00000 | $0.00305 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- modus-select-vs-dropdown-menu-solidjs — 86% identical, 196 lines differ
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}
/>
);
}
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.
- 4d ago First seen · 443 lines · 0 tokens per session scan A 541ecfe91b03
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.
Other cursor rules, from other repositories
react-ink-components
Guidelines for React components using Ink for terminal UI.
nextjs-patterns
// ✅ Correct: Default to Server Components export default async function Page({ params }) { const data = await getData(); return ; }.
react-native
React Native: mobile app development, navigation, native modules.
react
React: hooks, composition, performance patterns.
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.