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/testing)<a href="https://agentmods.dev/rules/ralfhuesing/computetoai/testing"><img src="https://agentmods.dev/badge/rules/ralfhuesing/computetoai/testing/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/testing"><img src="https://agentmods.dev/badge/rules/ralfhuesing/computetoai/testing.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.00263 |
| Opus 5.5 | $0.00000 | $0.00105 |
| Sonnet 5.5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
testing 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
Testpflicht
Jedes nicht-triviale Feature (jede Funktion mit einer Fallunterscheidung, einer Formel oder einem Seiteneffekt auf einen Store) bekommt mindestens einen Unit-Test. Trivial – und damit ohne eigenen Test zulässig – sind reine Datencontainer ohne Logik und einfache Weiterleitungen ohne eigene Berechnung.
- Framework:
pytest. - Ein Testmodul je Quellmodul (
tests/test_engine/test_store.pyfürsrc/compute_to_ai/engine/store.py), Teststruktur spiegelt Codestruktur. - Golden-/Referenztests für alles mit einem von Hand nachrechenbaren Ergebnis – der wichtigste Baustein für Vertrauen in größtenteils agentisch gebauten Code.
- Kein hartes Coverage-Ziel in Prozent – die Regel ist qualitativ, nicht ein Prozentwert.
- Ein Agent committet keine Änderung an
src/, für die die vorgeschriebenen Tests fehlen oder rot sind (siehegit-workflow.mdc).
Details/Begründung: Docs/11-Code-Standards-und-Projektstruktur.md.
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 · 18 lines · 0 tokens per session scan A 27d747b5c8ff
testing 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 263 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
testing
Vitest conventions and the mandatory unit-test set.
python-code-validator
Validate generated Python at every step, not once at the end.
architecture
This document outlines the fundamental architectural principles and patterns for the mcp-debug codebase. Adherence to these guidelines is mandatory to maintain a clean, decoupled, and testable system.
testing-standards
Testing standards for pytest, fixtures, async patterns, and test organization. Apply when writing or reviewing tests.
testing-standards
Cursor rule "testing-standards" from aaydin-tr/swagger-navigator-mcp, covering testing standards, test structure, coverage requirements, test organization and mocking guidelines.
qa-agent
QA workflow for reviewing stories, designing tests, and reporting verified defects.