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/bishopZ/2026-BoilerplateWrote 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/bishopz/2026-boilerplate/react-components)<a href="https://agentmods.dev/rules/bishopz/2026-boilerplate/react-components"><img src="https://agentmods.dev/badge/rules/bishopz/2026-boilerplate/react-components/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/bishopz/2026-boilerplate/react-components"><img src="https://agentmods.dev/badge/rules/bishopz/2026-boilerplate/react-components.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.00000 | $0.00185 |
| Opus 5.5 | $0.00000 | $0.00074 |
| Sonnet 5.5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
react-components 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 1mo 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 Component Rules
- Use arrow functions for all components. Never use the
classkeyword. - Use Chakra UI components (
Box,Flex,Container,Button, etc.) for layout and styling. - Use React Router's
LinkorRouterLinkfor client-side navigation. - Pages must include
<title>and<meta name="description">using React 19 document metadata. - Use lazy loading (
React.lazy) for page components inApp.tsx. - Prefer
useSelectoranduseDispatchfromreact-reduxfor Redux state access. - Avoid nested ternary operators. Use early returns or helper variables instead.
- Don't duplicate code. Extract shared logic into hooks (
src/client/hooks/) or UI components (src/client/ui/).
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.
- 1mo ago First seen · 16 lines · 0 tokens per session scan A e8c28f3a9013
react-components is a cursor rule published in the GitHub repository bishopZ/2026-Boilerplate (24 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 185 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-30.
Other cursor rules, from other repositories
family-instance-domain-actions
Family instance domain action implementation patterns.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values — and, outside the CLI and the PSL parser's grammar names, no Prisma version name before 8. Enforced by the no-family-vocabulary Biome plugin plus lint:framework-vocabulary.
no-target-branches
Never branch on target - use adapters instead.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-bare-casts
No bare as casts in production TypeScript. Use blindCast (value) from @internal/utils/casts as the auditable escape hatch, castAs (value) for declarative-only assertions, or rewrite to eliminate the cast. as const is exempt. Test files are exempt.