quick-stats
quick-stats retrieves and displays condensed Agent Monitor metrics in a single-line format, pulling from multiple API endpoints to summarize sessions, costs, events, tokens, and agent activity. Use it to quickly check system health and performance statistics without navigating to a full dashboard, with filtering options for cost-only, sessions-only, or token summaries depending on monitoring needs.
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor /tmp/quick-stats && cp -r /tmp/quick-stats/plugins/ccam-dashboard/skills/quick-stats ~/.claude/skills/quick-statsSKILL.md
# Quick Stats
One-line summary of key Agent Monitor metrics.
## Input
The user provides: **$ARGUMENTS**
Options: empty (default), "cost" (cost only), "sessions" (sessions only), "tokens" (token summary).
## Data Sources
| Endpoint | Returns |
|----------|---------|
| `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/pricing/cost` | `{ total_cost, breakdown }` |
| `GET /api/analytics` | tokens (total_input, total_output, total_cache_read, total_cache_write — baselines pre-summed), tool_usage, daily_sessions, daily_events |
| `GET /api/sessions?limit=1` | Most recent session for model/status |
## Output
Produce a single-line or compact summary:
**Default format:**
```
📊 127 sessions | 💰 $4.2301 total cost | 🔧 4,892 events | ⚡ 3 active | 🏆 Top tool: Read (1,204)
```
**Cost format:**
```
💰 Total: $4.2301 | Sonnet: $3.1200 | Opus: $0.9800 | Haiku: $0.1301 | Cache efficiency: 67%
```
**Sessions format:**
```
📋 127 total | ✅ 98 completed | ❌ 12 errored | 🏃 3 active | 💤 14 abandoned | Rate: 87%
```
**Tokens format:**
```
🔤 Input: 2.4M | Output: 890K | Cache Read: 1.8M | Cache Write: 340K
```
Keep it short enough to scan in a terminal prompt.Operate and maintain the local MCP server for this repository. Use for MCP tool updates, policy-guard changes, host configuration, and MCP runtime troubleshooting.
Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.
Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.
Review backend route and hook logic for regressions, data integrity risks, and missing tests.
Review React UI changes for behavior regressions, state consistency, and UX breakage.
Review MCP server changes for tool safety, schema quality, and host integration correctness.
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or adjusting safety policy flags.