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/dazhiyang/bsrnWrote 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/dazhiyang/bsrn/project-rules)<a href="https://agentmods.dev/rules/dazhiyang/bsrn/project-rules"><img src="https://agentmods.dev/badge/rules/dazhiyang/bsrn/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/dazhiyang/bsrn/project-rules"><img src="https://agentmods.dev/badge/rules/dazhiyang/bsrn/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.03931 | $0.03931 |
| Opus 5.5 | $0.01572 | $0.01572 |
| Sonnet 5.5 | $0.00786 | $0.00786 |
| Haiku 4.5 | $0.00393 | $0.00393 |
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.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🤖 Project Standards & Governance
This document defines the naming conventions, scientific symbols, and documentation standards used throughout the bsrn project.
Contributors and automated agents MUST read and apply the rules below before editing project code (especially §Documentation — function signatures and docstrings). Treat this file as binding, not background.
📏 Radiometric Parameters
Code variables and documentation MUST strictly adhere to the following table:
| Acronym | Code Name | Symbol | Full Name |
|---|---|---|---|
| GHI | ghi |
$G_h$ | global horizontal irradiance |
| BNI | bni |
$B_n$ | beam normal irradiance |
| DHI | dhi |
$D_h$ | diffuse horizontal irradiance |
| LWD | lwd |
$L_d$ | downward longwave radiation |
| LWU | lwu |
$L_u$ | upward longwave radiation |
| SWU | swu |
$S_u$ | upward shortwave radiation |
| NET | net |
$R_n$ | net radiation |
| SZA | zenith |
$Z$ | solar zenith angle |
| cosSZA | mu0 |
$\mu_0$ | cosine of SZA |
| SAA | azimuth |
$\phi$ | solar azimuth angle |
| GHIC | ghi_clear |
$G_{hc}$ | clear-sky GHI |
| BNIC | bni_clear |
$B_{nc}$ | clear-sky BNI |
| DHIC | dhi_clear |
$D_{hc}$ | clear-sky DHI |
| LWDC | lwd_clear |
$L_{dc}$ | clear-sky LWD |
| LWUC | lwu_clear |
$L_{uc}$ | clear-sky LWU |
| BNIE | bni_extra |
$E_{0n}$ | extraterrestrial BNI |
| GHIE | ghi_extra |
$E_{0}$ | extraterrestrial GHI |
| SC | solar_constant |
$E_{\text{sc}}$ | solar constant |
| CSI | kappa |
$\kappa$ | clear-sky index |
| k_t | kt |
$k_t$ | clearness index |
| K_t (daily) | Kt |
$K_t$ | daily clearness index |
| k_b | kb |
$k_b$ | beam transmittance |
| k_d | kd |
$k_d$ | diffuse transmittance |
| k | k |
$k$ | diffuse fraction |
| TMP | temp |
$T$ | air temperature |
| RH | rh |
$RH$ | relative humidity |
| SP | pressure |
$P$ | station pressure |
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 · 222 lines · 3,931 tokens per session scan A b34d0ff5d3ec
project-rules is a cursor rule published in the GitHub repository dazhiyang/bsrn (13 stars, last pushed 5mo ago), licensed MIT. It adds 3,931 tokens to every session, about $0.0157 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).