general-testing-rules

A set of general rules for how a coding agent should test software, based on a referenced documentation file.

In plain words
What is it for?
It is intended to guide an agent while it writes or checks tests.
Why use it?
It provides testing guidance in one place, but the excerpt does not show the specific rules.

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/jlevy/speculate/general-testing-rules
Clone the repo
git clone --depth 1 https://github.com/jlevy/speculate

Made for: Cursor.

Per session 12 This file is loaded in full into every session.
When invoked 12 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00012 $0.00012
Opus 5 $0.00006 $0.00006
Sonnet 5 $0.00002 $0.00002
Haiku 4.5 $0.00001 $0.00001

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

Security

Grade A, and why

general-testing-rules 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 yesterday.

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.

Origin

This is a copy

100% identical to general-testing-rules — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/general-testing-rules.mdc · 1 lines

What it actually says

../../docs/general/agent-rules/general-testing-rules.md

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. yesterday First seen · 1 lines · 12 tokens per session scan A db8e2024b67c

Subscribe to this mod's changes

general-testing-rules is a cursor rule published in the GitHub repository jlevy/speculate (34 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to general-testing-rules, differing in 0 lines, and is treated as a copy.