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/RalfHuesing/ComputeToAiWrote 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/ralfhuesing/computetoai/code-standards)<a href="https://agentmods.dev/rules/ralfhuesing/computetoai/code-standards"><img src="https://agentmods.dev/badge/rules/ralfhuesing/computetoai/code-standards/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/ralfhuesing/computetoai/code-standards"><img src="https://agentmods.dev/badge/rules/ralfhuesing/computetoai/code-standards.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.00000 | $0.00542 |
| Opus 5.5 | $0.00000 | $0.00217 |
| Sonnet 5.5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
code-standards 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
Code-Standards & Projektstruktur
Vollständige, verbindliche Fassung: Docs/11-Code-Standards-und-Projektstruktur.md. Kurzfassung:
- Einfacher Code statt Enterprise-Architektur: Early Returns statt verschachtelter Bedingungen, niedrige zyklomatische Komplexität (eine Funktion passt auf einen Bildschirm, max. eine Verschachtelungsebene), keine vorzeitige Abstraktion (kein Interface/keine "Manager"/"Factory"-Klasse ohne mindestens zwei konkrete Implementierungen – Rule of Three).
- Standardbibliotheken statt Eigenbau: NumPy/SciPy für Numerik, Pydantic für Schema/Validierung, offizielles MCP-Python-SDK für den Server.
- Drei Schichten mit fester Abhängigkeitsrichtung:
engine(domänenneutraler Kern, kenntfeatures/mcpnicht) ←features/*(untereinander unabhängig) ←mcp(nur Ein-/Ausgabe-Mapping, keine Fachlogik). - Tooling:
uv(Dependencies/Environment),ruff(Linting & Formatierung inkl. KomplexitätsregelC90),pytest(Tests),pyright(Typprüfung, Type Hints überall). - Warnungen sind Fehler:
pyrightläuft imstrict-Modus,ruffmit einem breiten Regel-Set über reine Formatierung hinaus (u. a. verpflichtende Typannotationen, Sicherheits-/Bug-Muster-Checks, keinprint(), kein auskommentierter Code),pytestmitfilterwarnings = ["error"]. Jede Warnung wird behoben, nicht unterdrückt – Ausnahme nur bei bekannten, unvermeidbaren Framework-Mustern (siehe „Strenge: Warnungen sind Fehler" inDocs/11). - Keine Projektplanung im Code: Kommentare/Docstrings verweisen nie auf
Docs/10-Roadmap.md, Meilenstein-/Epic-Nummern oderDocs/08-Offene-Fragen.md(sieheliving-documentation.mdc). - Projektstruktur (
src-Layout): siehe Diagramm inDocs/11-Code-Standards-und-Projektstruktur.md.
Bei Widerspruch zwischen dieser Kurzfassung und Docs/11 gilt Docs/11.
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 · 20 lines · 0 tokens per session scan A 296bfd4c0266
code-standards is a cursor rule published in the GitHub repository RalfHuesing/ComputeToAi (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 542 tokens. 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-31.
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).