agentmods.dev

code-standards

Project rules for code style, architecture, dependencies, testing, type checking, and the project’s folder structure.

In plain words
What is it for?
They guide Python code organization, dependency choices, type annotations, linting, formatting, tests, and strict static checks.
Why use it?
They reduce unnecessary complexity and make quality checks part of completing a change.

Cursor rule for Codex

0 1mo ago A scan 0 tokens original MIT
View the source file RalfHuesing/ComputeToAi
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/ralfhuesing/computetoai/code-standards
Clone the repo
git clone --depth 1 https://github.com/RalfHuesing/ComputeToAi

Made for: Codex.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 542 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00542
Opus 5 $0.00000 $0.00271
Sonnet 5 $0.00000 $0.00108
Haiku 4.5 $0.00000 $0.00054

Measured yesterday against content hash 296bfd4c0266, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.agents/rules/code-standards.mdc · 20 lines

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, kennt features/mcp nicht) ← features/* (untereinander unabhängig) ← mcp (nur Ein-/Ausgabe-Mapping, keine Fachlogik).
  • Tooling: uv (Dependencies/Environment), ruff (Linting & Formatierung inkl. Komplexitätsregel C90), pytest (Tests), pyright (Typprüfung, Type Hints überall).
  • Warnungen sind Fehler: pyright läuft im strict-Modus, ruff mit einem breiten Regel-Set über reine Formatierung hinaus (u. a. verpflichtende Typannotationen, Sicherheits-/Bug-Muster-Checks, kein print(), kein auskommentierter Code), pytest mit filterwarnings = ["error"]. Jede Warnung wird behoben, nicht unterdrückt – Ausnahme nur bei bekannten, unvermeidbaren Framework-Mustern (siehe „Strenge: Warnungen sind Fehler" in Docs/11).
  • Keine Projektplanung im Code: Kommentare/Docstrings verweisen nie auf Docs/10-Roadmap.md, Meilenstein-/Epic-Nummern oder Docs/08-Offene-Fragen.md (siehe living-documentation.mdc).
  • Projektstruktur (src-Layout): siehe Diagramm in Docs/11-Code-Standards-und-Projektstruktur.md.

Bei Widerspruch zwischen dieser Kurzfassung und Docs/11 gilt Docs/11.

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. yesterday First seen · 20 lines · 0 tokens per session scan A 296bfd4c0266

Subscribe to this mod's changes

code-standards is a cursor rule published in the GitHub repository RalfHuesing/ComputeToAi (0 stars, last pushed 1mo 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.

Data and AIPlanningTestingai-agentsfinancial-planningliquidity-planningmcp-servermodel-context-protocolretirement-planning
Related

Other cursor rules, from other repositories

swift-development

Swift development: SwiftUI, Combine, async/await, iOS patterns, and Apple platform conventions.

madebyaris/rakitui-ai · 0 tokens

cursorrules

When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.

CSOAI-ORG/social-media-ai-mcp · 80 tokens

cursorrules

This is an MCP (Model Context Protocol) server that provides Notion integration tools and AI agent workflows. Built with TypeScript, using the MCP SDK for server implementation.

tysoncung/notion-agent-hub · 437 tokens

lighter-safety

Safety contract for the Lighter MCP server. Apply whenever a lighter tool is invoked.

iamgoatedaf/lighter-mcp · 18 tokens

nix-security

Nix Security and Sandboxing.

ghuntley/groundhog · 489 tokens

memory-bank

You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…

alexeyleshchenko/fast-mcp-telegram · 1,623 tokens