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/syf2211/ruledoctorWrote 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/syf2211/ruledoctor/cursorrules)<a href="https://agentmods.dev/rules/syf2211/ruledoctor/cursorrules"><img src="https://agentmods.dev/badge/rules/syf2211/ruledoctor/cursorrules/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/syf2211/ruledoctor/cursorrules"><img src="https://agentmods.dev/badge/rules/syf2211/ruledoctor/cursorrules.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.00111 | $0.00111 |
| Opus 5.5 | $0.00044 | $0.00044 |
| Sonnet 5.5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
cursorrules 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
订单服务项目规则（demo）
硬性规则
- 金额必须用整数「分」，禁止用浮点。
- 错误必须用中文 ErrorXxx 抛出。
- 提交前必须运行 npm run lint。
- 严禁使用 any 类型。
- 日期格式统一 YYYY-MM-DD，禁止斜杠。
- 仓库禁止执行 git push --force。
- API 响应必须做异常兜底，不允许裸 throw。
- 注释一律使用中文。
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 · 13 lines · 111 tokens per session scan A bb6abf8eb5d4
cursorrules is a cursor rule published in the GitHub repository syf2211/ruledoctor (3 stars, last pushed 3mo ago), licensed MIT. It adds 111 tokens to every session, about $0.0004 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-30.
Other cursor rules, from other repositories
003-attribution
Prohibits AI attribution strings in commits, PR bodies, code comments, and client-facing content.
git-workflow
Git workflow: commits, branches, PRs, history management.
git-workflow
Git commit message conventions, PR workflow, and planning approach.
workflow
Rules for project workflows including Git, Taskmaster, Memory MCP, and Context7 MCP.
git-safety
Git Safety Rule - Require explicit permission for all git operations.
repository_initialization
Detailed steps for initializing a git repository when cloning the template directly.