Regression Watch
Detect quality and efficiency regressions over time using Agent Monitor data, rising...
Install
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill regression-watch -g -a claude-code -y- Repository
- hoangsonww/Claude-Code-Agent-Monitor1.1k
- Category
- AI and agents
- Updated
- 5d ago
- License
- MIT
- Context cost
- Lightabout 897 tokens
- Runs scripts
- No, instructions only
What it does
Detect quality and efficiency regressions over time using Agent Monitor data, rising error rate (APIError events), falling cache hit rate, growing compaction frequency, and climbing cost-per-session. Splits history into an earlier baseline window and a recent window and reports which metrics are getting worse, by how much, and where. Use when checking whether things are degrading or trending in the wrong direction.
Regression Watch
Detect whether Claude Code sessions are getting worse over time across quality and efficiency metrics, using Agent Monitor data.
Input
The user provides: $ARGUMENTS
This may be:
- empty or "all", check every regression metric (default)
- "errors", error-rate regression only
- "cache", cache hit-rate regression only
- "compaction", compaction-frequency regression only
- "cost", cost-per-session regression only
- A window like "last 30d" or "30 vs 90", set the recent vs baseline window sizes
Data Sources
| Endpoint | Returns |
|---|---|
GET /api/analytics | daily_events (365d), daily_sessions (365d), event_types, tokens (total_input, total_output, total_cache_read, total_cache_write, baselines pre-summed), avg_events_per_session |
GET /api/events?session_id=X | Event stream incl. APIError, Compaction, PreToolUse/PostToolUse, used to localize regressions to specific sessions |
GET /api/pricing/cost | { total_cost, breakdown[...] }, total cost to derive cost-per-session |
GET /api/pricing/cost/{sessionId} | Per-session cost, used to compare recent vs baseline session cost |
GET /api/workflows/{sessionId} | compaction (impact), errorPropagation (by depth), effectiveness, per-session quality signals |
GET /api/sessions?limit=N | Sessions with started_at, cost, metadata, to bucket sessions into time windows |
Report Sections
1. Windowing
Split history into a baseline window (older) and a recent window (newer).
Default: recent = last 30 days, baseline = the 30, 90 day range before it. Use
daily_events/daily_sessions for series metrics and GET /api/sessions?limit=N
to assign sessions to each window by started_at.
