usage-trends
Analyze Claude Code usage trends over time using the Agent Monitor's analytics API β daily session counts, daily event counts, token volumes by type, model distribution, tool usage rankings, and agent/event type distributions across 365-day retention windows.
Install / Use
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill usage-trendsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Our assessment of usage-trends
usage-trends scores 85/100 on our quality scale, 541st of 763 Operations skills we index.
Its SKILL.md is 3.3 KB long, well organised into 12 sections with 1 code example: a solid amount of guidance for an agent.
With 1,015 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so usage-trends is actively maintained.
- Our last check on 2026-11-05 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk β read a skill before letting an agent act on it.
usage-trends compared with similar skills
All 4 of these similar skills score higher than usage-trends; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| usage-trends (this skill)by hoangsonww | 85 | 1.0k | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 114.0k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 80.5k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 104.9k | 5d ago | MCP Server |
| crawl4aiby unclecode | 100 | 87.7k | 2d ago | MCP Server |
Frequently asked questions
- How do I install usage-trends?
- Run
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill usage-trends. The install tabs above show the steps for each supported agent. - Which AI agents does usage-trends work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is usage-trends safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is usage-trends still maintained?
- The repository was last updated about 2 months ago, so usage-trends is actively maintained.
Skill content
View source on GitHubname: usage-trends description: > Analyze Claude Code usage trends over time using the Agent Monitor's analytics API β daily session counts, daily event counts, token volumes by type, model distribution, tool usage rankings, and agent/event type distributions across 365-day retention windows.
Usage Trends
Analyze usage patterns and trends from the Agent Monitor analytics data.
Input
The user provides: $ARGUMENTS
Options: "last 7 days", "last 30 days", "last quarter", "peak hours", "tool trends", "model usage".
Data Sources
| Endpoint | Returns |
|----------|---------|
| GET /api/analytics | Comprehensive analytics object (see schema below) |
| GET /api/stats | { total_sessions, active_sessions, active_agents, total_agents, total_events, events_today, ws_connections, agents_by_status, sessions_by_status } |
| GET /api/sessions?limit=200 | Full session records with timestamps and metadata |
Analytics response schema (GET /api/analytics)
{
"overview": { "total_sessions", "active_sessions", "active_agents", "total_agents", "total_events" },
"tokens": {
"total_input": N, "total_output": N,
"total_cache_read": N, "total_cache_write": N
},
"tool_usage": [{ "tool_name": "...", "count": N }], // top 20
"daily_events": [{ "date": "YYYY-MM-DD", "count": N }], // 365 days
"daily_sessions": [{ "date": "YYYY-MM-DD", "count": N }], // 365 days
"agent_types": [{ "subagent_type": "task"|"explore"|null, "count": N }],
"event_types": [{ "event_type": "PreToolUse"|"PostToolUse"|..., "count": N }],
"avg_events_per_session": N,
"total_subagents": N,
"sessions_by_status": { "active": N, "completed": N, "error": N, "abandoned": N },
"agents_by_status": { "working": N, "completed": N, "error": N, ... }
}
Trend Analyses to Produce
1. Daily Activity Trend
Plot daily_sessions and daily_events for the requested period. Compute:
- Average sessions/day and events/day
- Week-over-week delta (%)
- Peak day and quietest day
2. Token Volume Trends
From analytics tokens (baselines are pre-summed into totals at the DB level):
- Total tokens:
total_input,total_output,total_cache_read,total_cache_write - Cache efficiency over time:
total_cache_read / (total_cache_read + total_input)β trending up = improving - Output intensity:
total_output / total_inputratio β high = Claude is verbose
3. Tool Usage Ranking
From tool_usage (top 20 tools by event count):
- Bar chart data (tool name β count)
- Tool diversity: unique tools used
- Subagent spawns: count of "Agent" tool uses (each = a subagent launched)
4. Model Distribution
From agent_types + per-session model field:
- Which models are used most frequently
- Subagent type distribution: main (null) vs task vs explore vs code-review
5. Session Health Distribution
From sessions_by_status:
- Completion rate:
completed / total Γ 100 - Error rate:
error / total Γ 100 - Abandoned rate:
abandoned / total Γ 100
6. Event Type Distribution
From event_types:
- PreToolUse/PostToolUse ratio (should be ~1:1; gap = tools failing)
- Compaction frequency relative to session count
- APIError count (quota hits, rate limits, overloaded)
Output
Markdown with tables and ASCII trend indicators (β²βΌβ). Include period comparison when applicable.
Related Skills
Agent-Reach
114.0kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu β one CLI, zero API fees.
headroom
80.5kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Scrapling
104.9kπ·οΈ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
crawl4ai
87.7kOfficial Crawl4AI Cloud: a hosted web scraping, extraction, and search API for AI agents. Free API key, 1,000 credits a month, no card. Fully open source: this repo is the Apache-2.0 crawler that powers it, and you can self-host it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit β see the Safety scan above for what the skill file itself contains.
