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/alonsarias/agent-rules/react-composition-patternsgit clone --depth 1 https://github.com/alonsarias/agent-rulesWhat 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.03324 |
| Opus 5 | $0.00000 | $0.01662 |
| Sonnet 5 | $0.00000 | $0.00665 |
| Haiku 4.5 | $0.00000 | $0.00332 |
Grade A, and why
react-composition-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.
How it starts
The opening of the file, as written. The whole thing — 632 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Composition Patterns
Composition patterns for building flexible, maintainable React components. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals.
1. Avoid Boolean Prop Proliferation
Impact: CRITICAL - Prevents unmaintainable component variants
Don't add boolean props like isThread, isEditing, isDMThread to customize behavior. Each boolean doubles possible states and creates unmaintainable conditional logic.
Incorrect: boolean props create exponential complexity
function Composer({
onSubmit,
isThread,
channelId,
isDMThread,
dmId,
isEditing,
isForwarding,
}: Props) {
return (
<div className="composer">
<Input />
{isDMThread ? (
<DMThreadHeader dmId={dmId} />
) : isThread ? (
<ThreadHeader channelId={channelId} />
) : null}
{isEditing ? (
<EditActions />
) : isForwarding ? (
<ForwardActions />
) : (
<SendActions onSubmit={onSubmit} />
)}
</div>
)
}
Correct: composition eliminates conditionals
// Channel composer
function ChannelComposer() {
return (
<ComposerProvider>
<ComposerFrame>
<ComposerInput />
<ComposerFooter>
<FormattingTools />
<EmojiPicker />
<SendButton />
</ComposerFooter>
</ComposerFrame>
</ComposerProvider>
)
}
// Thread composer - adds "also send to channel" field
function ThreadComposer({ channelId }: { channelId: string }) {
return (
<ThreadProvider channelId={channelId}>
<ComposerFrame>
<ComposerInput />
<AlsoSendToChannel />
<ComposerFooter>
<FormattingTools />
<SendButton />
</ComposerFooter>
</ComposerFrame>
</ThreadProvider>
)
}
// Edit composer - different footer actions
function EditComposer() {
return (
<EditProvider>
<ComposerFrame>
<ComposerInput />
<ComposerFooter>
<CancelButton />
<SaveButton />
</ComposerFooter>
</ComposerFrame>
</EditProvider>
)
}
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 · 632 lines · 0 tokens per session scan A 5fa4c2a573cc
react-composition-patterns is a cursor rule published in the GitHub repository alonsarias/agent-rules (4 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,324 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 cursor rules, from other repositories
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
test-patterns
Selenium pytest test patterns — data-driven tests, fixtures, error handling, and performance checks.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
core
The engineering contract for this repo lives in AGENTS.md (auto-loaded). Follow it. This rule only adds Cursor-specific behavior so the contract is not duplicated token-for-token on every request.
debugging
Debugging discipline. Apply when investigating a bug, test failure, or unexpected behavior.