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/commands/ofershap/cursor-usage-plugin/model-audit)<a href="https://agentmods.dev/commands/ofershap/cursor-usage-plugin/model-audit"><img src="https://agentmods.dev/badge/commands/ofershap/cursor-usage-plugin/model-audit/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/commands/ofershap/cursor-usage-plugin/model-audit"><img src="https://agentmods.dev/badge/commands/ofershap/cursor-usage-plugin/model-audit.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.00016 | $0.00226 |
| Opus 5.5 | $0.00006 | $0.00090 |
| Sonnet 5.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 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 model-audit — 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
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.
- 1mo ago First seen · 35 lines · 16 tokens per session scan A b2107bb01346
model-audit is a command published in the GitHub repository ofershap/cursor-usage-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 226 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to model-audit, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
decision-audit
Post-build decision ledger and pride gate; audit meaningful choices without changing code until revise.
prompt-eval-debug
Debug any prompt with a tiny eval suite (control, edge, boundary), failure diagnosis, and smallest next change, no blind rewrite.
tdd
Canon TDD (specify, encode, fulfill) with one test at a time, approval gates, and kitchen-cleaning refactor when needed.
thermo-nuclear-code-quality-review
Extremely strict maintainability review hunting for code-judo simplifications, giant files, and spaghetti-condition growth.
kuma:studio
📊 Kuma Studio — Web dashboard for gotchas, flows, workspace matrix, and metrics.
commit-same-branch
Commit on the current branch with conventional message.