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-react-key-warnings)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-react-key-warnings"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-react-key-warnings.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.04732 |
| Opus 5 | $0.00000 | $0.02366 |
| Sonnet 5 | $0.00000 | $0.00946 |
| Haiku 4.5 | $0.00000 | $0.00473 |
Grade A, and why
modus-react-key-warnings 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 — 806 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modus React Key Warnings - Essential Rules
🚨 CRITICAL: React Key Props with Modus Web Components
When using Modus Web Components in React, proper key handling is essential to prevent React warnings and ensure optimal performance.
❌ NEVER Do These
1. Missing Key Props on Mapped Components
// ❌ WRONG - No key prop
{
items.map((item) => (
<ModusWcMenuItem label={item.label} value={item.value} />
));
}
// ❌ WRONG - Using index only as key
{
items.map((item, index) => (
<ModusWcMenuItem key={index} label={item.label} value={item.value} />
));
}
2. Using Slots Instead of Props for Icons
// ❌ WRONG - Using slot content causes key issues
<ModusWcMenuItem label={item.label} value={item.value}>
{item.startIcon && (
<i className="modus-icons" slot="start-icon">
{item.startIcon}
</i>
)}
</ModusWcMenuItem>
3. Wrapping Web Components in Divs
// ❌ WRONG - Div wrapper interferes with web component
{
items.map((item) => (
<div key={item.value}>
<ModusWcMenuItem label={item.label} value={item.value} />
</div>
));
}
✅ ALWAYS Do These
1. Use Composite Keys for Web Components
// ✅ CORRECT - Composite key ensures uniqueness
{
items.map((item, index) => (
<ModusWcMenuItem
key={`${item.value}-${index}`}
label={item.label}
value={item.value}
start-icon={item.startIcon}
/>
));
}
2. Use Props Instead of Slots for Modus Components
// ✅ CORRECT - Use start-icon prop
<ModusWcMenuItem
key={`${item.value}-${index}`}
label={item.label}
value={item.value}
start-icon={item.startIcon}
sub-label={item.subLabel}
selected={item.selected}
disabled={item.disabled}
bordered={item.bordered}
/>
3. Handle Dynamic Content Properly
// ✅ CORRECT - Safe key generation
const generateKey = (item: MenuItem, index: number) => {
return item.value ? `${item.value}-${index}` : `item-${index}`;
};
{
items.map((item, index) => (
<ModusWcMenuItem
key={generateKey(item, index)}
label={item.label}
value={item.value}
/>
));
}
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 · 806 lines · 0 tokens per session scan A 998b8094c25a
modus-react-key-warnings 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 4,732 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.