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/udecode/plate-playground-template/reactgit clone --depth 1 https://github.com/udecode/plate-playground-templateWhat 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 | $0.00025 | $0.08580 |
| Opus 5 | $0.00013 | $0.04290 |
| Sonnet 5 | $0.00005 | $0.01716 |
| Haiku 4.5 | $0.00003 | $0.00858 |
Grade A, and why
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 yesterday.
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:
- react — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements
- Always use destructured props in function parameters
- Define TypeScript types inline with the destructured props
- Avoid creating separate interfaces for component props
- Avoid non-destructured props that require additional destructuring inside the component
- Use available UI components from the component library
- Use CSS variables from globals.css for consistent theming
- Use Tailwind v4 syntax (see Tailwind v4 Syntax)
- DO NOT add icon margin in Button, DropdownMenuItem: use gap-2 instead
- Use
useEffectEventto extract non-reactive logic from Effects (see Separating Events from Effects) - NEVER suppress the dependency linter with
eslint-disable- useuseEffectEventinstead - Use custom breakpoint syntax for responsive design (see App-Specific Rules)
Tailwind v4 Syntax
- Inline opacity: Use
/for opacity (bg-black/50 text-white/80)- v3:
bg-black bg-opacity-50 text-white text-opacity-80 - Removed:
bg-opacity-*,text-opacity-*,border-opacity-*
- v3:
- Renamed utilities:
shadow-sm→shadow-xs,rounded-sm→rounded-xs,blur-sm→blur-xs - CSS variables: Use parentheses
bg-(--brand-color)instead of bracketsbg-[--brand-color] - Important modifier: Exclamation mark at the end (
size-5!) instead of beginning (!size-5) - Descendant selectors: Use
**:for all descendants (replaces[&_*]:) and*:for direct children (replaces[&>*]:)- All descendants:
**:px-4instead of[&_*]:px-4 - Direct children:
*:px-4instead of[&>*]:px-4 - Element filtering:
*:[a]:underlineinstead of[&>a]:underline,**:[a]:underlineinstead of[&_a]:underline - Data attributes:
*:data-[slot=field-label]:flex-autoinstead of*:[[data-slot=field-label]]:flex-auto. Keep[[data-...]]if there are other selectors. - Context-aware (in-):
in-data-[slot=tooltip-content]:text-backgroundinstead of[[data-slot=tooltip-content]_&]:text-background
- All descendants:
- Composable variants: Chain variants together (
group-has-data-selected:opacity-100,data-highlighted:ring-2) - Canonical classes: Always prefer built-in utilities over arbitrary values (e.g.,
w-fullinstead ofw-[100%],translate-x-fullinstead oftranslate-x-[100%]) - Default changes: Border color now
currentColor(wasgray-200), ring width now 1px (was 3px)
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.
- yesterday First seen · 1,206 lines · 25 tokens per session scan A a63e70815a32
react is a cursor rule published in the GitHub repository udecode/plate-playground-template (240 stars, last pushed 11d ago), licensed MIT. It adds 25 tokens to every session and 8,580 once invoked, about $0.0001 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-08-30.
Other cursor rules, from other repositories
components
React component architecture for creating composable, accessible components with data attributes. Use when creating/updating composable components, not for higher-level feature/page components.
react
React patterns with destructured props, compiler optimization, Effects, and Tailwind v4 syntax. ALWAYS use when using React.
dev-browser
Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
browser-debug-setup
One-time setup for a persistent debug browser on 127.0.0.1:9222 for dev-browser --connect. Use when browser work is needed but no reusable debug browser is running yet.
agent-browser-issue
Open a concise GitHub follow-up for reusable browser-use limitations. Use when browser automation is blocked by a likely tool-side issue that is worth fixing separately, especially for clicks, dropdowns, file inputs, focus traps, or other repeatable agent/browser failures.
hard-cut
Remove a feature completely with no backward compatibility. Use when the user says "hard cut", "rip it out", "delete it", "unship", "kill this feature", or wants dead code removed instead of deprecated. Delete the surface, callers, tests, docs, comments, fallbacks, and stubs.