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/bishopz/2026-boilerplate/react-componentsgit clone --depth 1 https://github.com/bishopZ/2026-BoilerplateWhat 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.00185 |
| Opus 5 | $0.00000 | $0.00093 |
| Sonnet 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 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.
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.
- yesterday 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 (23 stars, last pushed 1mo 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
nextjs-standards
Cursor rule "nextjs-standards" from solana-foundation/solana-com, covering authoritative guidelines, code style, file & folder conventions, rendering strategy and state & data.
test-file-location
Keep test files in dedicated test directories.
30-scss-and-build
Sass 与构建约定（全局样式、变量注入、Vite base）.
00-project-core
本项目通用约定（结构、语言、改动边界）.
20-qa-json-content
题库 JSON（RichSegment）结构与文案规范.
10-vue-ts-conventions
Vue 3 + TypeScript 代码风格与组件约定.