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/model-auditgit 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.00016 | $0.00226 |
| Opus 5 | $0.00008 | $0.00113 |
| Sonnet 5 | $0.00003 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
model-audit 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:
- model-audit — 100% identical, 0 lines differ
What it actually says
Model Audit
Audit the team's model usage to find cost-saving opportunities:
- Call
get_model_usagewithstartDate: "30d"for a full month view. - Call
get_spendingwithallPages: trueto correlate model usage with spend. - Call
get_agent_editsandget_tabsto understand effectiveness per model tier.
Present findings as:
Model Distribution
- Pie chart description: what % of messages go to each model
- Premium vs standard vs budget model split
Cost Impact
- Estimated cost per model (messages × approximate cost per request)
- Which models are driving the most spend
Optimization Opportunities
- Users heavily using premium models for tasks that standard models handle well
- Specific recommendations: "User X could save ~$Y/month by switching from [model] to [model] for [task type]"
Action Items
- Ranked list of changes by estimated savings
- Suggested spend limits if appropriate
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 · 35 lines · 16 tokens per session scan A b2107bb01346
model-audit is a command published in the GitHub repository ofershap/cursor-usage (8 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 226 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.