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/peerigon/configsWrote 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/rules/peerigon/configs/coding-styleguide-react)<a href="https://agentmods.dev/rules/peerigon/configs/coding-styleguide-react"><img src="https://agentmods.dev/badge/rules/peerigon/configs/coding-styleguide-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/rules/peerigon/configs/coding-styleguide-react"><img src="https://agentmods.dev/badge/rules/peerigon/configs/coding-styleguide-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.00172 | $0.00172 |
| Opus 5.5 | $0.00069 | $0.00069 |
| Sonnet 5.5 | $0.00034 | $0.00034 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
coding-styleguide-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 2mo 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
- Use arrow functions for components
- Inline component props next to the component prop argument
- File order (MUST): put the main component (and its exported API) first; keep local helpers, secondary types, and minor constants below it — same rule as the JS/TS styleguide
- Derive state where possible
- Avoid unnecessary
useStateanduseEffect - Use
useEffectonly when synchronizing with external systems (for example browser APIs, subscriptions, timers, network interactions) - Keep effects small, deterministic, and cleanup-safe
- Avoid
useMemoanduseCallbackunless its absolutely necessary - Create a story for each React component if Storybook is used
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.
- 2mo ago First seen · 17 lines · 172 tokens per session scan A b110382daee4
coding-styleguide-react is a cursor rule published in the GitHub repository peerigon/configs (4 stars, last pushed today), licensed MIT. It adds 172 tokens to every session, about $0.0007 per session on Opus 5.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.
Other cursor rules, from other repositories
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
tanstack-react-router_routing
TanStack Router: Routing.
new-component
Workflow for creating new React components.