04-coding-guidelines

A set of coding rules for a Rust and Python WebView framework used in digital-content software, such as tools for creating media. It covers compatibility, naming, dependencies, testing, and development commands.

In plain words
What is it for?
Use it when writing or reviewing code, choosing libraries, checking Python and DCC compatibility, fixing lint issues, or keeping local and CI builds aligned.
Why use it?
It gives contributors consistent decisions to follow across local development, code review, and releases.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/loonghao/auroraview/04-coding-guidelines
Clone the repo
git clone --depth 1 https://github.com/loonghao/auroraview
Per session 254 This file is loaded in full into every session.
When invoked 254 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00254 $0.00254
Opus 5 $0.00127 $0.00127
Sonnet 5 $0.00051 $0.00051
Haiku 4.5 $0.00025 $0.00025

Measured 2d ago against content hash bfeeb49ecf4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.codebuddy/rules/04-coding-guidelines.mdc · 17 lines

What it actually says

编码规范与开发准则

  • 多搜索互联网寻找解决方案, 现在年份是2025.12, 搜索的时候需要按照最新的事件来
  • 我们的代码需要兼容python-3.7和所有DCC环境
  • 不需要做过多的总结,少用emoji表情在代码中。
  • 每次提交代码到远端需要解决Lint和clippy的风格问题
  • 避免optimized,fixed之类的词在我们的代码还有函数中
  • 我们的函数,还有函数名字的设计要简短精炼,多使用行业标准。
  • 不要自己造轮子,多用业内的成熟现有的crate
  • 如果CI有问题你可以自己使用github API根据对于的PR去看我们相关的错误信息
  • 为了保证我们开发的一致性,我们CI/CD和我们本地开发都多用just的命令去统一环境和管理
  • 需要保证我们PR阶段的测试与我们发布的构建应该一致
Changes

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.

  1. 2d ago First seen · 17 lines · 254 tokens per session scan A bfeeb49ecf4b

Subscribe to this mod's changes

04-coding-guidelines is a cursor rule published in the GitHub repository loonghao/auroraview (44 stars, last pushed 1mo ago), licensed MIT. It adds 254 tokens to every session, about $0.0013 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.