testing

A set of project rules for writing and changing tests. Tests are code that checks whether other code behaves as expected, including code that performs work later or repeatedly.

In plain words
What is it for?
Use it when working on tests that need asynchronous assertions, seeded fake resources, a standard test namespace, or checks that values are not empty before use.
Why use it?
It gives test changes a consistent structure and adds checks for common problems such as missing fake data or unsafe use of empty values. This makes the rules easier to follow across the project.

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/project-koku/koku-metrics-operator/testing
Clone the repo
git clone --depth 1 https://github.com/project-koku/koku-metrics-operator

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 81 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 $0.00000 $0.00081
Opus 5 $0.00000 $0.00041
Sonnet 5 $0.00000 $0.00016
Haiku 4.5 $0.00000 $0.00008

Measured 3d ago against content hash 164801020973, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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/testing.mdc · 10 lines

What it actually says

  • Use Eventually() and Consistently() for async assertions
  • Seed the fake client with required resources in BeforeEach
  • Default test namespace: koku-metrics-operator
  • Check for nil before dereferencing: Expect(value).NotTo(BeNil())
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. 3d ago First seen · 10 lines · 0 tokens per session scan A 164801020973

Subscribe to this mod's changes

testing is a cursor rule published in the GitHub repository project-koku/koku-metrics-operator (20 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 81 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-30.