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/inboxpraveen/Minimize-Cursor-CostWrote 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/inboxpraveen/minimize-cursor-cost/agent-efficiency)<a href="https://agentmods.dev/rules/inboxpraveen/minimize-cursor-cost/agent-efficiency"><img src="https://agentmods.dev/badge/rules/inboxpraveen/minimize-cursor-cost/agent-efficiency/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/inboxpraveen/minimize-cursor-cost/agent-efficiency"><img src="https://agentmods.dev/badge/rules/inboxpraveen/minimize-cursor-cost/agent-efficiency.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.00955 | $0.00955 |
| Opus 5.5 | $0.00382 | $0.00382 |
| Sonnet 5.5 | $0.00191 | $0.00191 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
agent-efficiency 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Efficiency Rules
Tool results, repeated searches, and correction loops usually cost more than the final response. Gather the minimum evidence needed for a correct change.
1. Plan Before Acting
Before issuing tool calls, decide internally (or state to the user in max 1 line) what file or symbol you are targeting and which tool is the cheapest way to find it. Skip planning chatter for trivial tasks (one-line edits, single-file reads).
2. Elastic Evidence Budget
| You need to… | Use… | Don't use… |
|---|---|---|
| Find an exact symbol or string | grep / ripgrep |
Semantic search, full file reads |
| Locate a file by name pattern | glob |
find recursive shell, listing all |
| Understand "how does X work" | Semantic search, then targeted read | Reading 10 files speculatively |
| Read a known function in a known file | Targeted read (offset/limit) |
Full-file read on a 1k-line file |
| Check a single command's output | Run it once | Run it, then --help, then again |
Use this evidence ladder:
- Use context already supplied. If the user gave a file path, start there; if the user gave an error, search for the error string first.
- Run one exact symbol, path, or error search. Prefer
grepfor a known symbol over reading a file to find it. - Read only the matching function or ±20 lines.
- Widen one step only when current evidence is insufficient or contradictory.
The "let me look around the repo first" instinct burns tokens fast. Only widen when the targeted approach failed. If two widened searches produce no new evidence, stop and ask one focused question or report the blocker.
3. Batch Independent Calls
If two reads/searches don't depend on each other, fire them in the same message. Serial chains of independent calls double latency and inflate context-handoff tokens.
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 · -17 lines · -70 tokens per session 3022a017bd81
- 1mo ago First seen · 109 lines · 1,025 tokens per session scan A fb2b2c7eabd3
agent-efficiency is a cursor rule published in the GitHub repository inboxpraveen/Minimize-Cursor-Cost (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 955 tokens to every session, about $0.0038 per session on Opus 5.5. 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
main-rules
Master rules for cursor-handbook - applies to all interactions.
pudo-core
Core PUDO workflow rules for all Cursor agent work.
vscode
VS Code: settings, extensions, workspace config.
sample_cursor_rule
React component best practices.
reply-tracker
Reply Tracker (also known as Reply Zero) lets the user which emails need a reply for them and those they're awaiting a reply on. It updates the labels for the thread automatically in Gmail.
emergency-fund
Size an emergency fund from essential spend and real risk factors — not a one-size 'six months' — with the funding timeline and where the money should sit. Use when asked how big should my emergency fund be, do I have enough saved, emergency fund or invest, or how many months of expenses do I need. Produces the…