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/jy315189/everything-cursorWrote 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/jy315189/everything-cursor/testing)<a href="https://agentmods.dev/rules/jy315189/everything-cursor/testing"><img src="https://agentmods.dev/badge/rules/jy315189/everything-cursor/testing/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/jy315189/everything-cursor/testing"><img src="https://agentmods.dev/badge/rules/jy315189/everything-cursor/testing.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.00000 | $0.00416 |
| Opus 5.5 | $0.00000 | $0.00166 |
| Sonnet 5.5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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 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 Rules
TDD Protocol
RED → GREEN → REFACTOR — no exceptions
- Define interfaces/types FIRST (the contract)
- Write failing tests (must fail for the right reason)
- Implement MINIMAL code to pass
- Verify all tests GREEN
- Refactor while keeping tests green
- Check coverage ≥ 80%
Test Structure: Arrange-Act-Assert
describe('[Module]', () => {
describe('[method]', () => {
it('[expected behavior in plain English]', async () => {
// Arrange — set up test data and mocks
// Act — call the function under test (ONE call)
// Assert — verify the outcome
})
})
})
Coverage Targets
| Area | Target | Rationale |
|---|---|---|
| Business logic (services) | 100% | Core value, must be correct |
| Utilities / helpers | ≥ 90% | Widely reused, high leverage |
| API handlers | ≥ 80% | Integration tests cover happy + error paths |
| UI components | ≥ 70% | Focus on interactions, not visual layout |
| Overall | ≥ 80% | Baseline confidence |
Mandatory Rules
- Every bug fix MUST include a regression test
- Tests MUST be independent (no shared mutable state)
- Test BEHAVIOR, not implementation details
- Mock external dependencies, use real logic for your code
- No
anyin test files — test types matter too - No
test.skipordescribe.skipin committed code - Flaky tests are bugs — fix or delete, never ignore
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 · 55 lines · 0 tokens per session scan A 7b2692536d22
testing is a cursor rule published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 416 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.
Other cursor rules, from other repositories
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.
debug-issue
When the user reports a bug, an error, or unexpected behavior. Enforces four structured phases — reproduction, failing test, root cause isolation, fix and verify — to stop guess-and-check loops.
common-testing
Testing requirements: 80% coverage, TDD workflow.
testing_rules
A testing guide covering TDD, where tests are written before code, and BDD, where expected behavior is described in Given-When-Then form.
tdd
Test-driven development — red-green-refactor cycle.
testing-standards
testing guidelines and expectations.