Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/autonomous-ai/autonomous-osnpx agentmods add rules/autonomous-ai/autonomous-os/testingWrote 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/autonomous-ai/autonomous-os/testing)<a href="https://agentmods.dev/rules/autonomous-ai/autonomous-os/testing"><img src="https://agentmods.dev/badge/rules/autonomous-ai/autonomous-os/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/autonomous-ai/autonomous-os/testing"><img src="https://agentmods.dev/badge/rules/autonomous-ai/autonomous-os/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.00202 | $0.00202 |
| Opus 5.5 | $0.00081 | $0.00081 |
| Sonnet 5.5 | $0.00040 | $0.00040 |
| Haiku 4.5 | $0.00020 | $0.00020 |
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
Testing Rules
Test Files
- Test files live next to the code they test:
internal/led/engine_test.go - Use standard
testingpackage — no external test frameworks - Table-driven tests preferred for multiple cases
Running Tests
go test ./... # All tests
go test ./internal/led/... # Single package
go test -run TestFunctionName # Single test
go test -v ./... # Verbose output
go test -race ./... # Race detector
Conventions
- Test function names:
TestMethodName_Scenario(e.g.TestEncodeColors_BufferLength) - Use
t.Errorfort.Fatalf— notpanicorlog.Fatalin tests - Test exported behavior, not internal implementation details
- Mock external dependencies (shell commands, hardware), not internal services
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 · 30 lines · 202 tokens per session scan A b9ac33acce96
testing is a cursor rule published in the GitHub repository autonomous-ai/autonomous-os (378 stars, last pushed 13d ago), licensed Apache-2.0. It adds 202 tokens to every session, about $0.0008 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
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.
debug-issue
When the user reports a bug, an error, or unexpected behavior. Enforces four structured phases — reproduction, failing test, root cause isolation, fix and verify — to stop guess-and-check loops.
common-testing
Testing requirements: 80% coverage, TDD workflow.
testing_rules
A testing guide covering TDD, where tests are written before code, and BDD, where expected behavior is described in Given-When-Then form.
tdd
Test-driven development — red-green-refactor cycle.
test-driven-development
Your Role and Mission: You are an expert TDD Software Developer AI specializing in Python. Your primary function is to write Python code by strictly adhering to the Test-Driven Development (TDD) methodology using the pytest framework. Your goal is to produce high-quality, robust, maintainable, and well-documented…