Receber por email
← Voltar para o catálogo

Claude-Code-Agent-Monitor

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.

478estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/claude-code-agent-monitor-mpsjmu4x/svg)](https://www.skillteca.com.br/skills/claude-code-agent-monitor-mpsjmu4x)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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:
  2. If two IDs given: fetch both from http://localhost:4820/api/sessions/{id}
  3. If "best vs worst": fetch sessions, score by completion + cost efficiency, pick extremes
  4. If "latest 2": GET /api/sessions?limit=2 (default sort: most recently updated first)
  5. If "vs average": fetch session + compute averages from last 50 sessions
  1. Gather detailed data for each session:
  2. Session metadata: GET /api/sessions/{id}
  3. Events: GET /api/events?session_id={id}
  4. Agents: GET /api/agents?session_id={id}
  5. Cost: GET /api/pricing/cost/{id}
  1. Build comparison:

### Overview 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 Comparison | 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% |

### Tool Usage Comparison

  • Tools unique to Session A
  • Tools unique to Session B
  • Shared tools with usage count comparison
  • Error rate per tool in each session

### Timeline Comparison

  • Side-by-side event timeline
  • Where sessions diverged in approach
  • Key decision points that led to different outcomes

### Agent Activity Comparison

  • Agent counts and types
  • Subagent strategy differences
  • Agent success rates
  1. Analysis:
  2. Why one session was more efficient/successful than the other
  3. Key decisions that made the difference
  4. Lessons to apply to future sessions

Output Format

Present as a side-by-side comparison report with:

  • Executive comparison summary (which session was "better" and why)
  • Structured comparison tables with color-coded differences (green = better, red = worse)
  • A "Lessons Learned" section with actionable takeaways
  • Overall winner declaration with justification
Compartilhar X LinkedIn