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.
npx agentmods add rules/inboxpraveen/minimize-cursor-cost/testsgit clone --depth 1 https://github.com/inboxpraveen/Minimize-Cursor-CostWhat 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 | $0.00000 | $0.00283 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
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 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.
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")overit("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
describeblock 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
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.
- yesterday First seen · 34 lines · 0 tokens per session scan A fcfaa275ffa7
tests is a cursor rule published in the GitHub repository inboxpraveen/Minimize-Cursor-Cost (6 stars, last pushed 16d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 283 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
sample_cursor_rule
React component best practices.
next
Next.js roof. Bundled docs for THIS next version. App vs Pages from the tree.
types
Type discipline — escape hatches are design bugs.
graphstack
GraphStack v4.7.1 — Orchestrated, graph-first, GNAP-tracked AI development (cross-platform).
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.
85-error-observability
Error handling, logging, and observability rules.