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-solidjs)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-select-vs-dropdown-menu-solidjs"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-select-vs-dropdown-menu-solidjs.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.03135 |
| Opus 5 | $0.00000 | $0.01568 |
| Sonnet 5 | $0.00000 | $0.00627 |
| Haiku 4.5 | $0.00000 | $0.00314 |
Grade A, and why
modus-select-vs-dropdown-menu-solidjs 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.
This is a copy
86% identical to modus-select-vs-dropdown-menu-react — 196 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ModusSelect vs ModusDropdownMenu in SolidJS
🚨 CRITICAL: ModusSelect Reliability Issues
Problem: ModusSelect component has unreliable event handling in SolidJS applications, especially with Chrome DevTools automation and testing.
Root Cause: ModusSelect events are inconsistent and may not fire reliably in SolidJS 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] = createSignal("");
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 SolidJS
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 SolidJS
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] = createSignal("");
const [isOpen, setIsOpen] = createSignal(false);
let dropdownRef: HTMLModusWcDropdownMenuElement | undefined;
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) {
dropdownRef.menuVisible = !isOpen();
setIsOpen(!isOpen());
}
};
const menuItems = [
{ label: "Option 1", value: "option1" },
{ label: "Option 2", value: "option2" },
{ label: "Option 3", value: "option3" },
];
return (
<ModusDropdownMenu
ref={(el: HTMLModusWcDropdownMenuElement) => (dropdownRef = el)}
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 · 453 lines · 0 tokens per session scan A 3348a42b422a
modus-select-vs-dropdown-menu-solidjs 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,135 tokens. A static security scan graded it A with 0 findings. It is 86% identical to modus-select-vs-dropdown-menu-react, differing in 196 lines, and is treated as a copy.
Other cursor rules, from other repositories
frontend-architecture
Cursor rule "frontend-architecture" from tomasz-tomczyk/crit, covering frontend architecture, two-paradigm page fork, module pattern, shared modules (used by both modes) and code-review modules (used only by code-review mode).
proxy-auth-transport
Every CLI command or browser UI action that calls a crit-web API must work in both modes.
hatch3r-design-system-detection
Mandatory detection of existing design tokens, theme primitives, and component library before AI agents author new UI components.
dev
AIOX agent @dev - Full Stack Developer.
nextjs-patterns
// ✅ Correct: Default to Server Components export default async function Page({ params }) { const data = await getData(); return ; }.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.