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/usage-report)<a href="https://agentmods.dev/commands/ofershap/cursor-usage-plugin/usage-report"><img src="https://agentmods.dev/badge/commands/ofershap/cursor-usage-plugin/usage-report/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/usage-report"><img src="https://agentmods.dev/badge/commands/ofershap/cursor-usage-plugin/usage-report.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.00017 | $0.00288 |
| Opus 5.5 | $0.00007 | $0.00115 |
| Sonnet 5.5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
usage-report 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 usage-report — 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
Usage Report
Generate a team usage report by following these steps:
- Call
get_team_overviewto get the high-level summary (members, spend, DAU, top models). - Call
get_spendingwithallPages: trueto get the full spending breakdown. - Call
get_model_usagefor the last 7 days to show recent model adoption trends. - Call
get_agent_editsfor the last 7 days to show AI effectiveness metrics.
Present the report in this structure:
Team Summary
- Total members, active members, DAU trend
- Total spend this cycle, average per member
- Billing cycle dates
Spending Breakdown
- Top 10 spenders with amounts
- Spend distribution (median, p75, p90, max)
- Anyone exceeding 3x the median (flag as potential concern)
Model Adoption
- Top 5 models by message volume
- Premium vs standard model split
- Any model concentration risks
AI Effectiveness
- Agent edit acceptance rate
- Tab completion acceptance rate
- Lines of code accepted vs suggested
Recommendations
- Cost optimization opportunities (reference the cursor-cost-optimization skill)
- Users who might benefit from model guidance
- Any anomalies worth investigating
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 · 46 lines · 17 tokens per session scan A 9cdc5f4ef7e5
usage-report is a command published in the GitHub repository ofershap/cursor-usage-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 288 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 usage-report, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
pricing-plan
Pricing and packaging audit — value metric, tiers, price corridor, research plan — plan only, no price edits.
comps
Run sold comparables for a subject property and estimate value from $/sqft.
zestimate
Get the Zestimate (home value) and rent Zestimate for a property.
usage-report
Generate a comprehensive team usage and spending report for the current billing cycle.
valuation-methods
../../vertical-plugins/equity-research-core/commands/valuation-methods.md.
cost-per-task
Compute cost-per-successful-task unit economics from usage and cost data, including retries, failures, and quality thresholds.