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/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/readme-md-guidelines)<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/readme-md-guidelines"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/readme-md-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.1 | $0.00004 | $0.00668 |
| Opus 5 | $0.00002 | $0.00334 |
| Sonnet 5 | $0.00001 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
readme-md-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 8d 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
README.md 指南
本规则集定义了 Laravel 包开发中 README.md 文件的编写指南和最佳实践，旨在确保包文档的清晰性、完整性和易用性。
1. 标题与简介
- 包名称:
README.md的顶部应包含清晰的包名称，通常作为一级标题。 - 简短描述: 紧随其后应提供一个简短、吸引人的包功能描述，让读者快速了解其用途。
- 状态徽章 (可选): 可以包含 CI/CD 状态、版本号、下载量等徽章，以提供快速概览。
2. 安装指南
- Composer: 详细说明如何通过 Composer 安装包，包括
composer require命令。 - 服务提供者: 如果需要，说明如何在
config/app.php中注册服务提供者。 - 发布配置/迁移: 如果包包含可发布的文件（如配置文件、迁移文件），提供发布命令。
3. 使用方法
- 基本用法: 提供清晰的代码示例，展示包的核心功能如何使用。
- 高级用法 (可选): 如果包有更复杂或高级的功能，可以提供额外的示例。
- 配置: 说明如何配置包，包括配置文件的结构和常用选项。
4. 贡献指南
- 如何贡献: 简要说明如何为包贡献代码，例如提交 Bug 报告、功能请求或 Pull Request。
- 代码风格: 如果有特定的代码风格要求，可以提及或链接到相关文档。
5. 测试
- 运行测试: 说明如何运行包的测试。
6. 许可证
- 许可证信息: 明确指出包的许可证类型（如 MIT、Apache 2.0），并建议包含许可证文件的链接。
7. 变更日志 (可选)
- 版本历史: 可以包含一个指向
CHANGELOG.md文件的链接，或直接在README.md中简要列出主要版本变更。
8. 示例结构
# Your Awesome Laravel Package
一个简短的描述，说明你的包做了什么。
[](https://example.com/ci)
## 安装
```bash
composer require vendor/package-name
发布配置 (可选)
php artisan vendor:publish --provider="Vendor\\PackageName\\PackageServiceProvider"
使用方法
// 你的代码示例
配置
说明配置选项。
贡献
欢迎贡献！请参阅 CONTRIBUTING.md 获取更多信息。
测试
composer test
许可证
本项目根据 MIT 许可证发布。
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.
- 8d ago First seen · 91 lines · 4 tokens per session scan A ca5a230e37c9
readme-md-guidelines is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (232 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 668 once invoked, about $0.0000 per session on Opus 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.