benchmark
Benchmark one session (or a small recent set) against the rolling average using Agent Monitor data — cost, total tokens, tool count, and workflow complexity score — and report where each metric lands as a percentile of the population. Tells you whether a session was normal, cheap, or an outlier. Use when judging whether a session was typical or out of band.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill benchmark --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Benchmark Score a session against the rolling population average and report its percentile on cost, tokens, tool count, and complexity using Agent Monitor data. ## Input The user provides: **$ARGUMENTS** This may be: - A single session ID — benchmark that session - "latest" — benchmark the most recent session - "latest N" — benchmark the N most recent sessions, each vs the average - empty — benchmark the most recent session (default) ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/sessions?limit=N` | Population of sessions with `cost`, `model`, `started_at`, `metadata` (turn_count, total_turn_duration_ms) — builds the rolling baseline | | `GET /api/pricing/cost/{sessionId}` | `{ total_cost, breakdown:[{ input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost }] }` — the target session's cost and tokens | | `GET /api/workflows/{sessionId}` | `complexity` (score), `stats` (tool/event counts), `toolFlow` (distinct tools used) — the target session's tool count and complexity | | `GET /api/analytics` | `avg_events_per_session`, `tool_usage`, `daily_sessions` — corroborates population-level averages | ## Report Sections ### 1. Build the Baseli
- Input
- Data Sources
- Report Sections
- 1. Build the Baseline
- 2. Measure the Target
- 3. Percentile and Deviation
- 4. Verdict
- Output
What does the benchmark skill do?
Benchmark one session (or a small recent set) against the rolling average using Agent Monitor data — cost, total tokens, tool count, and workflow complexity score — and report where each metric lands as a percentile of the population. Tells you whether a session was normal, cheap, or an outlier. Use when judging whether a session was typical or out of band.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill benchmark --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.