debug-live-issue
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data…
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
$ npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-compare --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/session-compareContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: session-compare description: > 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.
Compare two Claude Code sessions side-by-side using Agent Monitor data.
The user provides: **$ARGUMENTS**
This may be:
1. **Identify sessions to compare**:
2. **Gather detailed data** for each session:
3. **Build comparison**:
| Metric | Session A | Session B | Difference | |--------|-----------|-----------|-----------| | Status | completed | error | — | | Model | sonnet-4 | sonnet-4 | same | | Duration | 12m 34s | 45m 12s | +32m 38s | | Total Cost | $0.0234 | $0.1456 | +522% | | Events | 45 | 187 | +315% | | Tools Used | 8 | 12 | +4 | | Error Count | 0 | 7 | +7 | | Agents | 2 | 5 | +3 |
| Token Type | Session A | Session B | Difference | |-----------|-----------|-----------|-----------| | Input | N | N | ±N% | | Output | N | N | ±N% | | Cache Read | N | N | ±N% | | Cache Write | N | N | ±N% | | Efficiency | N% | N% | ±N% |
4. **Analysis**:
Present as a side-by-side comparison report with:
🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity, tool usage, and subagent orchestration, providing live analytics, a Kanban status board, status notifications, a cute buddy, & an interactive web UI/MacOS/Windows native app.
Repo: hoangsonww/Claude-Code-Agent-Monitor
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data…
MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start…
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored…
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or…
Push the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is…
Onboard quickly to this repository. Use when asked to understand architecture, locate ownership, choose the right module, or identify the correct commands and…