session-report

# Session Report Generate a detailed session report from the Claude Code Agent Monitor. ## Input The user provides: **$ARGUMENTS** This may be a session ID, "latest", or a date range like "last 24 hours". ## Data Sources All data comes from the Agent Monitor API at `http://localhost:4820`: | Endpoint | What it returns | |----------|----------------| | `GET /api/sessions/{id}` | Session with nested `.agents[]` and `.events[]` | | `GET /api/sessions?limit=50` | Session list with `agent_count`, `last_activity`, and **inline `cost`** per session (bulk pricing applied server-side) | | `GET /api/pricing/cost/{sessionId}` | `{ total_cost, breakdown: [{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] }` | | `GET /api/events?session_id={id}` | Event stream: each has `event_type`, `tool_name`, `summary`, `data` (JSON), `created_at` | ### Key data points available per session - **Status**: `active` / `completed` / `error` / `abandoned` - **Model**: primary model (e.g. `claude-sonnet-4-20250514`) - **Metadata (JSON)**: `thinking_blocks` count, `turn_count`, `total_turn_duration_ms`, `usage_extras` (service_tier, speed, inference_geo) - **Token usage per model**: Pricing breakdown reports `input_tokens`, `output_tokens`, `cache_read_tokens`, `cache_write_tokens` per model (baselines are pre-summed into these totals at the DB level) - **Cost formula**: `(tokens / 1,000,000) × rate_per_mtok` for each of 4 token types, using longest-m...