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/loonghao/auroraviewWrote 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/loonghao/auroraview/04-coding-guidelines)<a href="https://agentmods.dev/rules/loonghao/auroraview/04-coding-guidelines"><img src="https://agentmods.dev/badge/rules/loonghao/auroraview/04-coding-guidelines/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/loonghao/auroraview/04-coding-guidelines"><img src="https://agentmods.dev/badge/rules/loonghao/auroraview/04-coding-guidelines.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.00254 | $0.00254 |
| Opus 5.5 | $0.00102 | $0.00102 |
| Sonnet 5.5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
04-coding-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 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
编码规范与开发准则
- 多搜索互联网寻找解决方案, 现在年份是2025.12, 搜索的时候需要按照最新的事件来
- 我们的代码需要兼容python-3.7和所有DCC环境
- 不需要做过多的总结，少用emoji表情在代码中。
- 每次提交代码到远端需要解决Lint和clippy的风格问题
- 避免optimized，fixed之类的词在我们的代码还有函数中
- 我们的函数，还有函数名字的设计要简短精炼，多使用行业标准。
- 不要自己造轮子，多用业内的成熟现有的crate
- 如果CI有问题你可以自己使用github API根据对于的PR去看我们相关的错误信息
- 为了保证我们开发的一致性，我们CI/CD和我们本地开发都多用just的命令去统一环境和管理
- 需要保证我们PR阶段的测试与我们发布的构建应该一致
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 · 17 lines · 254 tokens per session scan A bfeeb49ecf4b
04-coding-guidelines is a cursor rule published in the GitHub repository loonghao/auroraview (47 stars, last pushed 18d ago), licensed MIT. It adds 254 tokens to every session, about $0.0010 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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.