react-patterns

A set of rules for writing React user interfaces with function-based components and correctly used hooks.

In plain words
What is it for?
Use it when creating or reviewing React components, deciding where to use hooks, and improving repeated or costly calculations and callbacks.
Why use it?
It keeps React code consistent and helps prevent mistakes such as breaking the Rules of Hooks or recalculating expensive work unnecessarily.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/agentsafety/clawcare/react-patterns
Clone the repo
git clone --depth 1 https://github.com/AgentSafety/ClawCare

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 57 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00057
Opus 5 $0.00000 $0.00028
Sonnet 5 $0.00000 $0.00011
Haiku 4.5 $0.00000 $0.00006

Measured yesterday against content hash a64d6b1da1cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

react-patterns 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.

tests/fixtures/cursor_project/.cursor/rules/react-patterns.mdc · 11 lines

What it actually says

React Patterns

  • Use functional components with hooks
  • Prefer useMemo and useCallback for expensive computations
  • Follow the Rules of Hooks
Changes

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.

  1. yesterday First seen · 11 lines · 0 tokens per session scan A a64d6b1da1cf

Subscribe to this mod's changes

react-patterns is a cursor rule published in the GitHub repository AgentSafety/ClawCare (5 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 57 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.