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/ofershap/cursor-usage-pluginWrote 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/ofershap/cursor-usage-plugin/cost-awareness)<a href="https://agentmods.dev/rules/ofershap/cursor-usage-plugin/cost-awareness"><img src="https://agentmods.dev/badge/rules/ofershap/cursor-usage-plugin/cost-awareness/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/ofershap/cursor-usage-plugin/cost-awareness"><img src="https://agentmods.dev/badge/rules/ofershap/cursor-usage-plugin/cost-awareness.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.00184 | $0.00184 |
| Opus 5.5 | $0.00074 | $0.00074 |
| Sonnet 5.5 | $0.00037 | $0.00037 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
cost-awareness 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.
This is a copy
100% identical to cost-awareness — 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.
What it actually says
When discussing model selection, code generation approaches, or AI-assisted workflows, keep cost implications in mind:
- Premium models (Opus, GPT-5) cost 10-50x more per request than standard models (Sonnet, GPT-4o, Gemini Flash).
- Most coding tasks — completions, inline edits, chat questions, code review — work well with standard-tier models.
- Reserve premium models for genuinely complex multi-step reasoning, architectural decisions, or agent mode tasks that require deep understanding.
- Agent mode loops are the #1 cause of unexpected spend spikes. Prefer focused, well-scoped agent tasks over open-ended exploration.
- If the user has the
cursor-usageMCP server configured, you can check their team's actual spending withget_team_overvieworget_spending.
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 · 13 lines · 184 tokens per session scan A f30e554008f1
cost-awareness is a cursor rule published in the GitHub repository ofershap/cursor-usage-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 184 tokens to every session, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cost-awareness, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
performance-rules
Performance optimization rules for Unity.
csharp-unity-conventions
C# coding conventions for Unity development.
monobehaviour-lifecycle
Correct usage of MonoBehaviour lifecycle methods.
security-and-builds
Security and build configuration rules.
serialization-rules
Unity serialization best practices.
shader-conventions
Conventions for Unity shader development.