hoangsonww/anomaly-alert
> Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps, APIError clusters), behavioral deviations from workflow intelligence (complexity score outliers, error propagation anomalies), and sessions with abnormal metadata (extreme turn_count, high thinking_blocks, zero turn_duration).
npx skills add https://github.com/hoangsonww/Claude-Code-Agent-Monitor --skill anomaly-alert
Detect anomalous sessions in Claude Code Agent Monitor data.
The user provides: $ARGUMENTS
This may be:
http://localhost:4820:GET /api/sessions?limit=500 — historical sessions for baselineGET /api/analytics — aggregated metricsGET /api/pricing/cost — cost data per sessionPresent as an Anomaly Report:
═══════════════════════════════════════════════
ANOMALY DETECTION REPORT
Analyzed: N sessions | Baseline: last 30 days
Anomalies found: N (🔴 N critical, 🟡 N warn, 🔵 N info)
═══════════════════════════════════════════════
For each anomaly:
Take hoangsonww/anomaly-alert from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.