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 commands/ofershap/cursor-usage/spend-checkgit 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.00017 | $0.00200 |
| Opus 5 | $0.00009 | $0.00100 |
| Sonnet 5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
spend-check 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- spend-check — 100% identical, 0 lines differ
What it actually says
Spend Check
Perform a quick spending health check:
-
If a user email was provided, call
get_user_deep_divefor that specific user and summarize their spend, model usage, and any concerns. -
If no email was provided: a. Call
get_spendingwithallPages: trueb. Calculate: total spend, median spend, top 3 spenders c. Flag anyone spending >3x the team median d. Flag anyone withhardLimitOverrideDollarsset to 0 who has high spend (approaching included limit) -
Present a concise summary:
- Total team spend this cycle
- Top 3 spenders
- Any flags or concerns
- One-line recommendation if applicable
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.
- 2d ago First seen · 24 lines · 17 tokens per session scan A 4d0b2253278b
spend-check is a command published in the GitHub repository ofershap/cursor-usage (8 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 200 once invoked, about $0.0001 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 commands, from other repositories
self-audit
Run npm run scan from the repository root. This repo must report L4 · Self-correcting.
review
Review the current diff for violations of the conventions in AGENTS.md and .cursor/rules/. Report findings ordered by severity; do not fix anything unless asked.
/spectra-propose
Create a complete change proposal with all artifacts in a single workflow.
/spectra-discuss
Have a focused discussion about a topic and reach a conclusion.
/spectra-ingest
Update an existing Spectra change from a plan file or conversation context.
add-memory
Add a new memory to the current project.