Cursor Usage Analytics

What it does

When your agent uses it

• Cursor analytics
• Cursor reporting
• Cursor dashboard

Example prompts

• “cursor analytics”
• “cursor usage”
• “cursor metrics”
• “/cursor-usage-analytics”

Requirements

• Compatibility (from SKILL.md): Designed for Claude Code
• Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(cmd:*)

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

1. 1Define the decision the metric supports and collect the minimum aggregation needed.
2. 2Review adoption, spend, model use, and policy signals against an agreed baseline.
3. 3Share only authorized aggregate findings and document remediation/enablement actions.
4. 4Reassess access and retention regularly; do not repurpose analytics without approval.

What it can do on your machine

Read from SKILL.md and the folder at commit 23ea8d4. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Edit
  • Bash(cmd:*)

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • cursor

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • cursor.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Designed for Claude Code

  From compatibility in the SKILL.md frontmatter.

Context cost

Cursor Usage Analytics loads about 2.1k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 527 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~67

When it runs · the whole SKILL.md, loaded when a task matches

~2.1k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 23ea8d4, republished under its MIT licence (© jeremylongshore). 527 words, ~2,121 tokens.

name

cursor-usage-analytics

description

Track and analyze Cursor usage metrics via admin dashboard: requests, model usage, team productivity, and cost optimization. Triggers on "cursor analytics", "cursor usage", "cursor metrics", "cursor reporting", "cursor dashboard", "cursor ROI".

allowed-tools

Read, Write, Edit, Bash(cmd:*)

compatibility

Designed for Claude Code

version

1.19.0

license

MIT

author

Jeremy Longshore <jeremy@intentsolutions.io>

tags

saas, cursor, analytics, dashboard

┌─ Dashboard ────────────────────────────────────────────┐
│                                                        │
│  Total Requests This Month:  12,847                    │
│  Fast Requests Remaining:    2,153 / 15,000            │
│  Active Users:               28 / 30 seats             │
│  Most Used Model:            Claude Sonnet (62%)       │
│                                                        │
│  ┌─ Usage Trend ─────────────────────────────────┐     │
│  │  ▆▆▇▇██▇▆▇█▇▇▆▅                              │     │
│  │  Mon Tue Wed Thu Fri Sat Sun                   │     │
│  └───────────────────────────────────────────────┘     │
│                                                        │
│  ┌─ Top Users ───────────────────────────────────┐     │
│  │  alice@co.com     847 requests  (Sonnet)      │     │
│  │  bob@co.com       623 requests  (GPT-4o)      │     │
│  │  carol@co.com     591 requests  (Auto)        │     │
│  └───────────────────────────────────────────────┘     │
│                                                        │
└────────────────────────────────────────────────────────┘

1. Default to Auto mode
   - Cursor routes simple queries to cheaper models
   - Only uses premium models when complexity warrants it

2. Educate team on model selection
   - Simple questions → cursor-small or GPT-4o-mini
   - Standard coding → GPT-4o or Claude Sonnet
   - Hard problems only → Claude Opus, o1 (these burn quota fast)

3. Reduce round-trips
   - Write detailed prompts (fewer back-and-forth turns)
   - Use @Files instead of @Codebase (less context = faster)
   - Start new chats instead of continuing stale ones

4. BYOK for power users
   - Heavy users can use their own API keys
   - Their requests don't count against team quota

# Cursor Usage Report - [Month Year]

## Summary
- Active users: X / Y seats (X% utilization)
- Total AI requests: X,XXX
- Fast request quota usage: XX%
- Monthly cost: $X,XXX

## Adoption Trends
- New users onboarded: X
- Users showing increased usage: X
- Inactive users (0 requests): X

## Model Usage Distribution
- Claude Sonnet: XX%
- GPT-4o: XX%
- Auto: XX%
- Other: XX%

## Recommendations
- [Scale / optimize / train based on data]

Time saved per developer per day:         ~1 hour (conservative estimate)
Working days per month:                   22
Developer hourly cost (fully loaded):     $75
Monthly time savings per developer:       22 hours × $75 = $1,650

Cursor cost per developer:                $40/month (Business)
ROI per developer:                        $1,650 - $40 = $1,610/month
ROI multiple:                             41x

Break-even: developer saves >32 minutes/month

1. Run team training session (30 min demo of Chat + Composer)
2. Share the cursor-hello-world skill for hands-on practice
3. Create project rules (.cursor/rules/) so AI gives better results
4. Assign "AI Champion" per team to share tips and answer questions
5. Set a 30-day adoption goal and review progress

1. Review model usage -- are users defaulting to expensive models?
2. Enable Auto mode as team default
3. Train on efficient prompting (fewer turns = fewer requests)
4. Consider BYOK for top 5 users (offloads their usage from team quota)
5. Evaluate upgrading to more seats or Enterprise plan

1. Check if project rules are configured (AI is less useful without them)
2. Verify indexing works (poor @Codebase = poor experience)
3. Look for extension conflicts (GitHub Copilot still enabled?)
4. Survey team for friction points and address them

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references) in skills/.curated/cursor-usage-analytics of jeremylongshore/tons-of-skills-marketplace.

• SKILL.md
• references/analytics-api.md
• references/analytics-overview.md
• references/benchmarking.md
• references/best-practices.md
• references/custom-reports.md
• references/dashboard-views.md
• references/errors.md
• references/examples.md
• references/key-metrics.md
• references/optimization-insights.md

Open the folder on GitHubat commit 23ea8d4