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/ofershap/cursor-usage/cost-awarenessgit clone --depth 1 https://github.com/ofershap/cursor-usageWhat 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.00184 | $0.00184 |
| Opus 5 | $0.00092 | $0.00092 |
| Sonnet 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cost-awareness — 100% identical, 0 lines differ
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.
- yesterday 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 (8 stars, last pushed 6mo ago), licensed MIT. It adds 184 tokens to every session, about $0.0009 per session on Opus 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
docs-i18n-parity
Guide docs must stay in sync across all VitePress locales (en + pt-BR, es, zh-CN, hi-IN).
checks
How to add or modify a scanner check.
http
HTTP handler conventions.
cursorrules
When the user asks you to implement a feature or fix an issue, use mooquickstart to atomically create and claim the task in a single step with complete specifications.
swap-asset-resolution
Resolve IronWallet swap assets from catalog tools, not memory.
seed-phrase-handling
Never expose IronWallet recovery phrases or private keys.