03-testing

03-testing is a cursor rule for Cursor from the-missing-pink/ai-repository-security-baseline. It costs 0 tokens per session (204 once invoked), scanned A, original, Apache-2.0.

A set of rules requiring tests, linting, and type checking before each commit. Test-driven development, or TDD, means writing tests around expected behavior; these rules also require tests for new code and bug fixes.

In plain words
What is it for?
Use it when adding functions, methods, or endpoints, fixing bugs, testing error paths, or checking behavior at input boundaries.
Why use it?
It helps catch regressions and edge-case failures before code is committed, while preventing tests from being skipped, deleted, or weakened just to make a build pass.

Cursor rule for Cursor

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/the-missing-pink/ai-repository-security-baseline/03-testing
Clone the repo
git clone --depth 1 https://github.com/the-missing-pink/ai-repository-security-baseline

Made for: Cursor.

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

agentmods badge for 03-testing

README.md
[![agentmods](https://agentmods.dev/badge/rules/the-missing-pink/ai-repository-security-baseline/03-testing.svg)](https://agentmods.dev/rules/the-missing-pink/ai-repository-security-baseline/03-testing)
Your own site
<a href="https://agentmods.dev/rules/the-missing-pink/ai-repository-security-baseline/03-testing"><img src="https://agentmods.dev/badge/rules/the-missing-pink/ai-repository-security-baseline/03-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 204 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.1 $0.00000 $0.00204
Opus 5 $0.00000 $0.00102
Sonnet 5 $0.00000 $0.00041
Haiku 4.5 $0.00000 $0.00020

Measured 5d ago against content hash 6948644edf6a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

03-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 5d 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.

.cursor/rules/03-testing.mdc · 28 lines

What it actually says

Testing Requirements

Test-Before-Commit Policy

  • Run the full test suite before every commit.
  • Run linting and type checking before every commit.
  • Never skip tests with --no-verify, skip, xfail, or equivalent.
  • Never delete or disable existing tests to make new code pass.

Coverage

  • All new functions, methods, and endpoints must have tests.
  • Bug fixes must include regression tests.
  • Test edge cases, error paths, and boundary conditions.

Quality

  • Tests must be deterministic: no random data, no time-dependent assertions.
  • Use mocks and stubs for external services.
  • Test names must describe the scenario and expected behavior.
  • Follow Arrange-Act-Assert pattern.
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. 5d ago First seen · 28 lines · 0 tokens per session scan A 6948644edf6a

Subscribe to this mod's changes

03-testing is a cursor rule published in the GitHub repository the-missing-pink/ai-repository-security-baseline (10 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 204 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.