What is component-patterns?

A set of rules for writing React components in a design system. React components are reusable interface pieces, and TypeScript interfaces describe the data they accept.

Guiding developers to use functional React components and TypeScript interfaces for component props.

It keeps components consistent by setting conventions for their structure and properties.

component-patterns — Cursor rule by theamazingwolf

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/theamazingwolf/cursor-bridge-mcp/component-patterns

Clone the repo

git clone --depth 1 https://github.com/theamazingwolf/cursor-bridge-mcp

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 41 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00041
Opus 5	$0.00000	$0.00020
Sonnet 5	$0.00000	$0.00008
Haiku 4.5	$0.00000	$0.00004

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

Security

Grade A, and why

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

src/__tests__/fixtures/.cursor/rules/component-patterns.mdc · 10 lines

What it actually says