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/j4flmao/agent-skillsWrote 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/j4flmao/agent-skills/testing-requirements)<a href="https://agentmods.dev/rules/j4flmao/agent-skills/testing-requirements"><img src="https://agentmods.dev/badge/rules/j4flmao/agent-skills/testing-requirements/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/j4flmao/agent-skills/testing-requirements"><img src="https://agentmods.dev/badge/rules/j4flmao/agent-skills/testing-requirements.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.00013 | $0.00321 |
| Opus 5.5 | $0.00005 | $0.00128 |
| Sonnet 5.5 | $0.00003 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
testing-requirements 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 Requirements
Cursor/AI MUST follow these rules regarding tests.
1. Zero-Prompt Testing
When generating a new business logic function or class, you must proactively generate (or update) the corresponding unit test without waiting for the user to explicitly say "write tests for this".
2. The Arrange-Act-Assert (AAA) Pattern
All tests must strictly follow the AAA pattern for readability. Do not mix assertions with setup code.
// BAD
expect(calculator.add(2, 2)).toBe(4);
// GOOD
it('should return the sum of two positive numbers', () => {
// Arrange
const calc = new Calculator();
const a = 2;
const b = 2;
// Act
const result = calc.add(a, b);
// Assert
expect(result).toBe(4);
});
3. Test Edge Cases, Not Just Happy Paths
Do not only test the optimal scenario. You must include tests for:
- Null, undefined, or empty inputs.
- Out-of-bounds values (negative numbers, extreme lengths).
- Expected exception throwing (e.g.,
expect(() => fn(null)).toThrow()).
4. Mocking Boundaries
If the function interacts with a Database, File System, or external API, you MUST mock that dependency in the unit test. Do not write unit tests that perform real HTTP requests.
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 · 43 lines · 13 tokens per session scan A 99e1c71ebeb9
testing-requirements is a cursor rule published in the GitHub repository j4flmao/agent-skills (33 stars, last pushed 10d ago), licensed MIT. It adds 13 tokens to every session and 321 once invoked, about $0.0001 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-09-05.
Other cursor rules, from other repositories
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.