agentmods.dev

usage-report

A command that gathers team activity, model use, accepted AI edits, and spending for the current billing period.

In plain words
What is it for?
Use it to review team size and activity, spending distributions, popular models, AI-assisted coding results, and possible cost or training actions.
Why use it?
It puts usage and cost information in one report, making unusual spending and adoption patterns easier to spot.

Command

2 6mo ago A scan 17 tokens copy · 100% MIT
View the source file ofershap/cursor-usage-plugin
Install

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.

agentmods
npx agentmods add commands/ofershap/cursor-usage-plugin/usage-report
Clone the repo
git clone --depth 1 https://github.com/ofershap/cursor-usage-plugin
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 288 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00288
Opus 5 $0.00009 $0.00144
Sonnet 5 $0.00003 $0.00058
Haiku 4.5 $0.00002 $0.00029

Measured yesterday against content hash 9cdc5f4ef7e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

Origin

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.

commands/usage-report.md · 46 lines

What it actually says

Usage Report

Generate a team usage report by following these steps:

  1. Call get_team_overview to get the high-level summary (members, spend, DAU, top models).
  2. Call get_spending with allPages: true to get the full spending breakdown.
  3. Call get_model_usage for the last 7 days to show recent model adoption trends.
  4. Call get_agent_edits for 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
Changes

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.

  1. yesterday First seen · 46 lines · 17 tokens per session scan A 9cdc5f4ef7e5

Subscribe to this mod's changes

usage-report is a command published in the GitHub repository ofershap/cursor-usage-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 288 once invoked, about $0.0001 per session on Opus 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.

Analytics and metricsCode reviewData and AIclaude-codecursor-idecursor-pluginmcpusage
Related

Other commands, from other repositories

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.

paladini/harness-score · 0 tokens

ship-and-observe

Take merged, green code to a verified, monitored production release — deploy, confirm the revision is live, smoke-test, observe, and roll back if needed.

kensaurus/cursor-kenji · 31 tokens

refactor

Systematic refactoring: analyze → split → extract → verify behavior, with no truncation or omitted lines.

kensaurus/cursor-kenji · 21 tokens

review-code

Agent review pass plus manual checklist for correctness, security, performance, and accessibility.

kensaurus/cursor-kenji · 15 tokens

auth-flows

Read-only audit of app-layer auth — route×gate matrix, getSession vs getUser, middleware-as-only-gate.

kensaurus/cursor-kenji · 24 tokens

codemod-safety

Audit a codemod or bulk mechanical transform for behavior-preservation — report only.

kensaurus/cursor-kenji · 16 tokens