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-checkbox-value-inversion-react)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-checkbox-value-inversion-react"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-checkbox-value-inversion-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.03357 |
| Opus 5 | $0.00000 | $0.01679 |
| Sonnet 5 | $0.00000 | $0.00671 |
| Haiku 4.5 | $0.00000 | $0.00336 |
Grade A, and why
modus-checkbox-value-inversion-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.
How it starts
The opening of the file, as written. The whole thing — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ModusWcCheckbox Value Inversion Bug in React
🚨 CRITICAL BUG: Checkbox Value Inversion
Problem: The ModusWcCheckbox component has an inverted value property that causes unexpected behavior in React applications.
Bug Details:
- When checkbox is checked:
target.valuereturnsfalse - When checkbox is unchecked:
target.valuereturnstrue - This is the opposite of what developers expect
- The bug occurs in the
inputChangeevent'starget.valueproperty
❌ The Problem in Action
❌ Expected vs Actual Behavior
// ❌ WRONG: This doesn't work as expected
function CheckboxComponent() {
const [isChecked, setIsChecked] = useState(false);
const handleChange = (event: CustomEvent<InputEvent>) => {
const value = (event.target as HTMLModusWcCheckboxElement).value; // ❌ This is inverted!
console.log("Checkbox value:", value); // false when checked, true when unchecked
setIsChecked(value); // ❌ This sets wrong state
};
return (
<ModusWcCheckbox value={isChecked} onInputChange={handleChange}>
Checkbox Label
</ModusWcCheckbox>
);
}
❌ Common Mistakes
// ❌ WRONG: Direct value usage
const handleChange = (event: CustomEvent<InputEvent>) => {
const value = (event.target as HTMLModusWcCheckboxElement).value; // ❌ Inverted value
setState(value); // ❌ Wrong state
};
// ❌ WRONG: Assuming value matches checked state
const handleChange = (event: CustomEvent<InputEvent>) => {
const value = (event.target as HTMLModusWcCheckboxElement).value; // ❌ false when checked
const isChecked = value; // ❌ Wrong assumption
updateUI(isChecked); // ❌ Wrong UI state
};
✅ Solution: Invert the Value
✅ Correct Pattern: Invert the Value
// ✅ CORRECT: Always invert the value
function CheckboxComponent() {
const [isChecked, setIsChecked] = useState(false);
const handleChange = (event: CustomEvent<InputEvent>) => {
const value = (event.target as HTMLModusWcCheckboxElement).value;
const actualChecked = !value; // ✅ CORRECT: Invert the value
console.log("Checkbox value:", value); // false when checked
console.log("Actual checked:", actualChecked); // true when checked
setIsChecked(actualChecked);
};
return (
<ModusWcCheckbox value={isChecked} onInputChange={handleChange}>
Checkbox Label
</ModusWcCheckbox>
);
}
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 · 493 lines · 0 tokens per session scan A 8a17f257d270
modus-checkbox-value-inversion-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,357 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
mobx-devtools
Instructions for using MobX DevTools, including a browser extension and development component for inspecting application state changes.
mobx-strict-mode
Guidance for enabling MobX strict mode, which requires observable state changes to happen inside actions.
apollo-devtools
A debugging guide for Apollo Client DevTools, a browser extension for inspecting GraphQL requests and Apollo's local cache. It covers queries, mutations, subscriptions, variables, responses, and errors.
nextjs-patterns
// ✅ Correct: Default to Server Components export default async function Page({ params }) { const data = await getData(); return ; }.
error-handling-rules
description: Rules for implementing error handling in Next.js 14 using error.tsx files. globs: /app/error.tsx.
react-native
React Native: mobile app development, navigation, native modules.