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/holtwood/awesome-cursorrules-zh/react-component-guidelinesgit clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zhWrote 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/holtwood/awesome-cursorrules-zh/react-component-guidelines)<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/react-component-guidelines"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/react-component-guidelines.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00088 |
| Opus 5 | $0.00000 | $0.00044 |
| Sonnet 5 | $0.00000 | $0.00018 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
react-component-guidelines 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
- 确保所有组件都是可重用的并遵循现有的设计模式。
- 确保所有组件都是响应式和可访问的。
- 使用 Tailwind CSS 进行样式设计，遵循定义的调色板。
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 · 8 lines · 0 tokens per session scan A 6a3870382a41
react-component-guidelines is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (232 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 88 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-09-03.
Other cursor rules, from other repositories
nextjs-material-ui-tailwind-css-cursorrules-prompt
Cursor rules for Next.js development with Material UI and Tailwind CSS integration.
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and Tailwind CSS integration.
react-chakra-ui-cursorrules-prompt-file
Cursor rules for React development with Chakra UI integration.
react-components-creation-cursorrules-prompt-file
Cursor rules for React component creation and development.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
ui-patterns
This project follows consistent UI patterns for authentication flows, form handling, and user feedback. All components use modern React patterns with TypeScript and Tailwind CSS.