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.
npx agentmods add rules/pueraeternis/agentic-project-template/11-testing-standardsgit clone --depth 1 https://github.com/pueraeternis/agentic-project-templateWrote 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/pueraeternis/agentic-project-template/11-testing-standards)<a href="https://agentmods.dev/rules/pueraeternis/agentic-project-template/11-testing-standards"><img src="https://agentmods.dev/badge/rules/pueraeternis/agentic-project-template/11-testing-standards.svg" alt="Measured on agentmods" 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 | $0.00005 | $0.00580 |
| Opus 5 | $0.00003 | $0.00290 |
| Sonnet 5 | $0.00001 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
11-testing-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 4d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Standards
Testing is an integral part of implementation.
New functionality should be accompanied by appropriate validation.
Project-specific testing requirements are defined in ENGINEERING.md.
Testing Philosophy
Tests should verify:
- business behavior;
- domain rules;
- validation logic;
- component interactions;
- observable system behavior.
Avoid testing implementation details.
Prefer behavior over implementation.
Testing Levels
Use the lowest practical testing level.
Typical hierarchy:
- Unit tests
- Integration tests
- End-to-end or system tests
Prefer fast, isolated tests whenever practical.
Unit Tests
Unit tests should:
- run quickly;
- be deterministic;
- test one behavior;
- avoid external dependencies.
Unit tests should not require:
- network access;
- external APIs;
- production databases;
- live LLMs;
- external infrastructure.
Integration Tests
Integration tests verify interactions between components.
Typical examples:
- persistence;
- service integrations;
- API boundaries;
- external adapters;
- messaging;
- workflow execution.
Use isolated environments whenever practical.
Deterministic Testing
Tests should produce identical results on every execution.
Avoid dependencies on:
- current time;
- execution order;
- random values without fixed seeds;
- mutable external state.
Use fixtures and controlled test data.
Regression Testing
Whenever practical, every bug fix should include a regression test.
Preferred workflow:
Failing Test
↓
Implement Fix
↓
Passing Test
The regression test should reproduce the original issue.
Validation
Before completing implementation:
- execute the project's validation commands;
- run applicable tests;
- review acceptance criteria;
- verify repository consistency.
Use the validation workflow documented in ENGINEERING.md.
Test Design
Tests should be:
- readable;
- focused;
- independent;
- deterministic;
- maintainable.
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.
- 4d ago First seen · 193 lines · 5 tokens per session scan A 31b54a280db0
11-testing-standards is a cursor rule published in the GitHub repository pueraeternis/agentic-project-template (2 stars, last pushed 2mo ago), licensed MIT. It adds 5 tokens to every session and 580 once invoked, about $0.0000 per session on Opus 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-31.
Other cursor rules, from other repositories
testing-standards
Testing standards and patterns for all code.
testing-patterns
Testing patterns and best practices for PRPM codebase with Vitest.
testing-pyramid-agent
Provides guidance on testing pyramid principles and how to analyze test distribution. Use this rule when discussing test distribution, test strategy, or when analyzing test coverage across unit, integration, and E2E tests.
flutter-testing-rules
Specifies testing guidelines for Flutter projects, covering unit, widget, and integration tests.
testing
Rules for testing Astro projects, including unit tests and end-to-end testing.
test-engineer
Test Engineer agent.