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.
npx agentmods add rules/julianoczkowski/create-trimble-app/modus-checkbox-value-inversion-react-shortgit 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-short)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-checkbox-value-inversion-react-short"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-checkbox-value-inversion-react-short.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.00228 | $0.00228 |
| Opus 5 | $0.00114 | $0.00114 |
| Sonnet 5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
modus-checkbox-value-inversion-react-short 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 2d 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.
What it actually says
Modus Checkbox Value Inversion - Short
Critical bug fix for ModusWcCheckbox value property inversion.
Key Rules
- Always invert checkbox value property -
const actualChecked = !valuefrominputChangeevent - Use wrapper components - Create React wrapper to handle inversion automatically
- Never trust the raw value - The
valueproperty is inverted (false when checked, true when unchecked) - Handle in event handlers - Invert value in
onInputChangeevent handler - Use utility functions - Create helper functions for value inversion
- Test thoroughly - Verify checkbox behavior matches expected state
- Document the bug - Make team aware of this critical issue
Reference
For detailed bug explanation, wrapper component patterns, and utility functions, fetch the full rule: modus-checkbox-value-inversion-react
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.
- 2d ago First seen · 24 lines · 228 tokens per session scan A 665754243170
modus-checkbox-value-inversion-react-short is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It adds 228 tokens to every session, about $0.0011 per session on Opus 5. 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
slate-patch
Fix Slate v2 bugs in one pass with reproduction, behavior tests, architecture/DX/perf pressure, proactive rearchitecture when the patch is not the cleanest long-term shape, and final autoreview.
mobx-devtools
利用 MobX DevTools 调试 MobX 应用程序.
mobx-strict-mode
为 MobX 强制执行严格模式以获得更好的调试体验.
apollo-devtools
建议使用 Apollo Client DevTools 进行调试.
debugging
Bug-fixing discipline - build a red feedback loop before hypothesizing, ship every fix with a regression test. Apply whenever diagnosing or fixing a bug, failure, or regression.
error-handling-rules
description: Rules for implementing error handling in Next.js 14 using error.tsx files. globs: /app/error.tsx.