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-best-practices)<a href="https://agentmods.dev/rules/julianoczkowski/create-trimble-app/modus-react-best-practices"><img src="https://agentmods.dev/badge/rules/julianoczkowski/create-trimble-app/modus-react-best-practices.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.03088 |
| Opus 5 | $0.00000 | $0.01544 |
| Sonnet 5 | $0.00000 | $0.00618 |
| Haiku 4.5 | $0.00000 | $0.00309 |
Grade A, and why
modus-react-best-practices 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-solidjs-best-practices — 88% identical, 142 lines differ
How it starts
The opening of the file, as written. The whole thing — 509 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modus React Best Practices for Vite + SWC
🏗️ Component Architecture
✅ Single Configurable Component Pattern
CRITICAL: Create one configurable component instead of multiple specific components.
// ✅ CORRECT: Single configurable component
function ModusButton({
variant = "primary",
size = "md",
disabled = false,
children,
...props
}: ModusButtonProps) {
const baseClasses =
"inline-flex items-center justify-center font-medium transition-colors focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring disabled:pointer-events-none disabled:opacity-50";
const variantClasses = {
primary: "bg-primary text-primary-foreground hover:bg-primary/90",
secondary: "bg-secondary text-secondary-foreground hover:bg-secondary/90",
destructive:
"bg-destructive text-destructive-foreground hover:bg-destructive/90",
outline:
"border border-border bg-background hover:bg-muted hover:text-muted-foreground",
ghost: "hover:bg-muted hover:text-muted-foreground",
link: "text-primary underline-offset-4 hover:underline",
};
const sizeClasses = {
sm: "h-9 px-3 text-sm",
md: "h-10 px-4 py-2",
lg: "h-11 px-8",
icon: "h-10 w-10",
};
return (
<ModusWcButton
className={`${baseClasses} ${variantClasses[variant]} ${sizeClasses[size]}`}
disabled={disabled}
{...props}
>
{children}
</ModusWcButton>
);
}
// ❌ WRONG: Multiple specific components
function PrimaryButton({ children, ...props }) {
/* ... */
}
function SecondaryButton({ children, ...props }) {
/* ... */
}
function DestructiveButton({ children, ...props }) {
/* ... */
}
✅ Component Composition Pattern
// ✅ CORRECT: Component composition
function Card({ children, className, ...props }: CardProps) {
return (
<div
className={`bg-card text-card-foreground border border-border rounded-lg ${className}`}
{...props}
>
{children}
</div>
);
}
function CardHeader({ children, className, ...props }: CardHeaderProps) {
return (
<div className={`flex flex-col space-y-1.5 p-6 ${className}`} {...props}>
{children}
</div>
);
}
function CardTitle({ children, className, ...props }: CardTitleProps) {
return (
<div
className={`text-2xl font-semibold leading-none tracking-tight ${className}`}
{...props}
>
{children}
</div>
);
}
function CardContent({ children, className, ...props }: CardContentProps) {
return (
<div className={`p-6 pt-0 ${className}`} {...props}>
{children}
</div>
);
}
// Usage
<Card>
<CardHeader>
<CardTitle>Card Title</CardTitle>
</CardHeader>
<CardContent>
<div>Card content</div>
</CardContent>
</Card>;
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 · 509 lines · 0 tokens per session scan A c8b911cd0dc9
modus-react-best-practices 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,088 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
hatch3r-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and Tailwind CSS integration.
react-components-creation-cursorrules-prompt-file
Cursor rules for React component creation and development.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
chakra-ui---responsive-design
Guidance for making Chakra UI layouts adapt to different screen sizes. It uses responsive style values, breakpoints, layout components, and conditional display rules for phones, tablets, and desktops.