session-compare
Compare two sessions side-by-side using Agent Monitor data — per-model token usage (input/output/cache_read/cache_write + compaction baselines), pricing engine cost breakdowns, workflow intelligence (complexity scores, tool flow transitions, subagent effectiveness), session metadata (thinking_blocks, turn_count, turn_duration_ms, usage_extras), and full event timelines with all 10+ event types.
Profile →npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-compare --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.
# Session Compare Compare two Claude Code sessions side-by-side using Agent Monitor data. ## Input The user provides: **$ARGUMENTS** This may be: - Two session IDs: "abc123 def456" - "best vs worst" — compare highest and lowest productivity sessions - "latest 2" — compare the two most recent sessions - A session ID + "vs average" — compare one session against the baseline ## Procedure 1. **Identify sessions to compare**: - If two IDs given: fetch both from `http://localhost:4820/api/sessions/{id}` - If "best vs worst": fetch sessions, score by completion + cost efficiency, pick extremes - If "latest 2": `GET /api/sessions?limit=2` (default sort: most recently updated first) - If "vs average": fetch session + compute averages from last 50 sessions 2. **Gather detailed data** for each session: - Session metadata: `GET /api/sessions/{id}` - Events: `GET /api/events?session_id={id}` - Agents: `GET /api/agents?session_id={id}` - Cost: `GET /api/pricing/cost/{id}` 3. **Build comparison**: ### Overview Comparison | Metric | Session A | Session B | Difference | |--------|-----------|-----------|-----------| | Status | completed | error | — | | Model | sonnet-4 | sonnet-4 | same | | Duratio
- Input
- Procedure
- Output Format
What does the session-compare skill do?
Compare two sessions side-by-side using Agent Monitor data — per-model token usage (input/output/cache_read/cache_write + compaction baselines), pricing engine cost breakdowns, workflow intelligence (complexity scores, tool flow transitions, subagent effectiveness), session metadata (thinking_blocks, turn_count, turn_duration_ms, usage_extras), and full event timelines with all 10+ event types.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-compare --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.