A set of rules for writing tests, which are small programs that check whether code behaves correctly. It keeps tests short, focused, and consistent with the surrounding test file.

Use it when adding or changing tests: choose clear names, reuse existing fixtures, follow the file's structure, and keep each test focused on one behavior.

It reduces duplicated test logic, unnecessary setup, and tests that are hard to understand or maintain. It also prevents adding snapshots or private-method tests without a reason.

tests — Cursor rule for Cursor by inboxpraveen/Minimize-Cursor-Cost

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.

Clone the repo

git clone --depth 1 https://github.com/inboxpraveen/Minimize-Cursor-Cost

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/inboxpraveen/minimize-cursor-cost/tests/github.svg)](https://agentmods.dev/rules/inboxpraveen/minimize-cursor-cost/tests)

Your own site

<a href="https://agentmods.dev/rules/inboxpraveen/minimize-cursor-cost/tests"><img src="https://agentmods.dev/badge/rules/inboxpraveen/minimize-cursor-cost/tests/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/inboxpraveen/minimize-cursor-cost/tests"><img src="https://agentmods.dev/badge/rules/inboxpraveen/minimize-cursor-cost/tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 343 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00343
Opus 5.5	$0.00000	$0.00137
Sonnet 5.5	$0.00000	$0.00069
Haiku 4.5	$0.00000	$0.00034

Measured 1mo ago against content hash 77c9ddbd2f4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

lean-cursor/.cursor/rules/tests.mdc · 34 lines

What it actually says

Test File Rules

Output discipline

Write the minimum test that proves the behavior
No "describe the purpose" comments — test names are the documentation
Don't repeat the implementation logic inside the test

Test naming

Match the naming style already in the file
Prefer: it("returns X when Y") over it("test case 1")
Don't rename existing tests

Mocks

Reuse existing mock factories/fixtures — don't create new ones unless missing
Inline small mock data; reference fixtures for large data
Show only the mock lines that changed

When adding tests

Add to the existing describe block if one exists — don't create a new one
Follow the existing Arrange/Act/Assert structure (or Given/When/Then)
One assertion focus per test — don't bundle unrelated assertions

Never

Don't add snapshot tests unless asked
Don't test private methods unless asked
Don't add setup/teardown unless required for the new test
Don't regenerate passing tests while adding new ones

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.

1mo ago Changed 77c9ddbd2f4e
1mo ago First seen · 34 lines · 0 tokens per session scan A fcfaa275ffa7

Subscribe to this mod's changes

tests is a cursor rule published in the GitHub repository inboxpraveen/Minimize-Cursor-Cost (10 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 343 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.

Claude Code Testing claude-ai claude-skills cursor cursor-rules vibe-coding

tests

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Test File Rules

Output discipline

Test naming

Mocks

When adding tests

Never

What this file has done since we first saw it

Other cursor rules, from other repositories

ci-cd

integration-testing

mock-patterns

testing-standards

testing

80-testing-quality