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/usrrname/cursorrulesWrote 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/commands/usrrname/cursorrules/react)<a href="https://agentmods.dev/commands/usrrname/cursorrules/react"><img src="https://agentmods.dev/badge/commands/usrrname/cursorrules/react/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/usrrname/cursorrules/react"><img src="https://agentmods.dev/badge/commands/usrrname/cursorrules/react.svg" alt="Reviewed on agentmods" width="80" 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.00320 |
| Opus 5.5 | $0.00000 | $0.00128 |
| Sonnet 5.5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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 1mo 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
/react
Apply React with TypeScript best practices.
Usage
/react [component-or-hook]
When to Invoke
Use this command when:
- Creating React components
- Building custom hooks
- Managing React state
- Handling events with TypeScript
Standards Applied
Component Patterns
- FC type or explicit function types
- Props interfaces with readonly
- Proper children typing
- Event handler types
Hooks
- useState with generics
- useReducer typed actions
- useRef for elements/values
- Custom hooks with full signatures
Props Design
- Optional props with
? - Discriminated unions for variants
- ComponentProps for wrappers
- forwardRef typing
Examples
Input
function Button({ onClick, children }) {
return <button onClick={onClick}>{children}</button>;
}
Output
interface ButtonProps {
readonly variant: 'primary' | 'secondary';
readonly children: React.ReactNode;
readonly onClick?: () => void;
}
export const Button: React.FC<ButtonProps> = ({
variant,
children,
onClick
}) => {
return (
<button className={variant} onClick={onClick}>
{children}
</button>
);
};
Agent
Uses BasicBitch with Spellchuck for documentation.
Related
/typescript- TypeScript fundamentals/nextjs- Next.js React patterns
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.
- 1mo ago First seen · 77 lines · 0 tokens per session scan A 83ff1e4fc4fa
react is a command published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 320 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-08-31.
Other commands, from other repositories
generate-types
Generate TypeScript types or type definitions from schemas, APIs, or data structures.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.