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 skills/ofershap/cursor-usage-plugin/cursor-usage-analysisnpx skills add ofershap/cursor-usage-plugin --skill cursor-usage-analysisgit clone --depth 1 https://github.com/ofershap/cursor-usage-pluginWhat 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.00051 | $0.01535 |
| Opus 5 | $0.00026 | $0.00767 |
| Sonnet 5 | $0.00010 | $0.00307 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
cursor-usage-analysis 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.
This is a copy
100% identical to cursor-usage-analysis — 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Usage Analysis
You have access to Cursor Enterprise API data through the cursor-usage MCP server. This skill teaches you how to interpret that data correctly — the API returns raw numbers, but understanding what they mean requires context that isn't in the docs.
Before You Start
- Use the
get_team_overviewtool first to orient yourself — it gives you the big picture in one call. - For user-specific questions, use
get_user_deep_divewith their email. - For time-range analysis, all analytics tools accept
startDateandendDate.
Critical Data Interpretation Rules
Spending
spendCentsis the total spend including the subscription-included amount. To get overage (extra cost beyond the plan), subtractincludedSpendCents.- A user with
spendCents: 5000andincludedSpendCents: 4000has $10 in overage, not $50 in total extra cost. fastPremiumRequestscounts requests to premium/expensive models (Opus, GPT-5, etc.) that consume the fast request quota faster.- Spend limits (
hardLimitOverrideDollars) only cap overage spend, not included spend. A limit of $0 means "no overage allowed," not "no usage allowed."
Lines of Code Metrics
totalLinesAddedincludes ALL lines: agent-suggested, tab-completed, and manually typed. It is NOT a measure of AI productivity.acceptedLinesAddedis the real AI productivity metric — lines the user explicitly accepted from AI suggestions.- The acceptance rate (
acceptedLinesAdded / totalLinesAdded) is misleading because the denominator includes manual edits. UsetotalAccepts / totalAppliesfor the true AI acceptance rate. - Agent mode lines are counted in
totalLinesAddedbut may not appear inacceptedLinesAddedbecause agent mode auto-applies changes.
Request Types
composerRequests: Inline edit requests (Cmd+K / Ctrl+K)chatRequests: Chat panel conversationsagentRequests: Agent mode (autonomous multi-step tasks)usageBasedReqs: Requests that count against the usage-based billing tier (overage)cmdkUsages: Legacy name for composer/inline edit usagebugbotUsages: Automated bug detection runs
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 120 lines · 51 tokens per session scan A 958b8a3f2034
cursor-usage-analysis is a skill published in the GitHub repository ofershap/cursor-usage-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,535 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cursor-usage-analysis, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
editor-scripting
Extending the Unity Editor with custom inspectors, editor windows, property drawers, gizmos, and Scene View overlays using UI Toolkit.
addressables-assets
Managing assets with the Addressables system for async loading, memory management, and remote content delivery.
animation-systems
Unity animation workflows including Animator Controller, Timeline, DOTween, and sprite animation for 2D.
audio-systems
Audio implementation patterns including AudioSource, AudioMixer, spatial audio, and audio management.
ecs-dots
Entity Component System development with Unity Entities, Jobs, and Burst for high-performance simulation.
monobehaviour-patterns
Comprehensive guide to MonoBehaviour lifecycle, async patterns with Awaitable, and common Unity design patterns.