sample_cursor_rule

A set of written rules for building React user-interface components, including how to structure them, name parts, and define their data.

In plain words
What is it for?
Use it when creating or reviewing React components that should follow functional-component, hooks, composition, and naming guidelines.
Why use it?
It gives the coding agent consistent project conventions, reducing unclear or mismatched component code.

Cursor rule

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/zanzythebar/cursor-rules/sample_cursor_rule
Clone the repo
git clone --depth 1 https://github.com/ZanzyTHEbar/cursor-rules
Per session 88 This file is loaded in full into every session.
When invoked 88 The same file — it is already loaded in full.
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.00088 $0.00088
Opus 5 $0.00044 $0.00044
Sonnet 5 $0.00018 $0.00018
Haiku 4.5 $0.00009 $0.00009

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

Security

Grade A, and why

sample_cursor_rule 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.

test_samples/sample_cursor_rule.mdc · 19 lines

What it actually says

React Component Guidelines

Use functional components with hooks. Prefer composition over inheritance. Always add PropTypes or TypeScript interfaces.

Naming Conventions

  • PascalCase for component names
  • camelCase for props and handlers
  • Prefix event handlers with "handle"
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 · 19 lines · 88 tokens per session scan A 4acfe97404cb

Subscribe to this mod's changes

sample_cursor_rule is a cursor rule published in the GitHub repository ZanzyTHEbar/cursor-rules (3 stars, last pushed 4mo ago), licensed MIT. It adds 88 tokens to every session, about $0.0004 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-31.