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/SourceLin/sourcelin-cloud-blogWrote 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/sourcelin/sourcelin-cloud-blog/project-rules)<a href="https://agentmods.dev/rules/sourcelin/sourcelin-cloud-blog/project-rules"><img src="https://agentmods.dev/badge/rules/sourcelin/sourcelin-cloud-blog/project-rules/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/sourcelin/sourcelin-cloud-blog/project-rules"><img src="https://agentmods.dev/badge/rules/sourcelin/sourcelin-cloud-blog/project-rules.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.00297 | $0.00297 |
| Opus 5.5 | $0.00119 | $0.00119 |
| Sonnet 5.5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
project-rules 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 2mo 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
Cursor 统一规则入口
请以下列规则源为准：
rules/frontend-platform.mdrules/design-system-layering.mdrules/ui-design-system-core.mdrules/ui-vue-components.mdrules/ui-page-boundaries.mdrules/ui-scss-tokens.mdrules/documentation-sync.md
请以下列技能源为准：
skills/README.mdskills/sourcelin-ui-refactor/SKILL.mdskills/sourcelin-ui-refactor/reference.md
请以下列架构说明为准：
README.mdAGENTS.mddocs/frontend-architecture.mddocs/style-asset-ledger.md
执行要求：
- 改规则，只改
rules/ - 改技能，只改
skills/ - 架构边界、路由协议、请求约定和样式资产变更后，同步检查文档与轻量入口
- 首屏加载统一走
SSkeleton与共享 skeleton 组件；增量加载保持轻 spinner / quiet loading - 不在
.cursor/中重复维护整套规则或技能正文
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.
- 2mo ago First seen · 38 lines · 297 tokens per session scan A d113e7b5d10f
project-rules is a cursor rule published in the GitHub repository SourceLin/sourcelin-cloud-blog (11 stars, last pushed 4mo ago), licensed MIT. It adds 297 tokens to every session, about $0.0012 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
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).