Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill regression-alertgit clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-MonitorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/regression-alert)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/regression-alert"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/regression-alert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/regression-alert"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/regression-alert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00073 | $0.00889 |
| Opus 5 | $0.00036 | $0.00445 |
| Sonnet 5 | $0.00015 | $0.00178 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
regression-alert scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Read-only **except** the explicit "arm" path, which is the only write. Never mutate alert rules otherwise. If `curl` cannot reach `http://localhost:4820`, tell the user to start the dashboard with `npm start` from the How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regression Alert
Detect whether Claude Code reliability is getting worse period-over-period, and
optionally arm an alert so it never has to be checked by hand again. Scope is
reliability/failures only — for cache/cost/compaction drift, use ccam-insights'
regression-watch instead.
Input
The user provides: $ARGUMENTS
This may be:
- empty or "all" — check error rate and tool-failure rate (default)
- "errors" — APIError-rate regression only
- "tools" — tool-failure-rate regression only
- a window like "7 vs 7" or "30 vs 30" — recent vs baseline window sizes (default: last 7 days vs the prior 7)
- "arm" — after reporting, also create an alert rule via
POST /api/alerts/rules(only on explicit request)
Data Sources
| Endpoint | Returns |
|---|---|
GET /api/analytics |
daily_events (365d), daily_sessions (365d), event_types — split into recent vs baseline windows to compute per-window failure rates |
GET /api/events?session_id=X |
Per-session stream — localize a regression to the sessions driving it |
GET /api/alerts/rules |
Existing alert rules — check whether a matching reliability rule already exists before arming a new one |
POST /api/alerts/rules |
Create a new alert rule (only when the user says "arm") |
Report Sections
1. Windowing
Split history into a recent window (newer) and a baseline window (the equal-length period just before it). Default: recent = last 7 days, baseline = the prior 7. Use daily_events/daily_sessions to bucket counts by day.
2. Error-Rate Regression
- Per window:
error rate = APIError count / total events. - Compare recent vs baseline. Flag if recent is higher. Report absolute change (pp) and relative change (%), plus the recent sessions contributing the most
APIErrorevents.
3. Tool-Failure-Rate Regression
- Per window:
tool-failure rate = (PreToolUse − PostToolUse) / PreToolUse. - Compare recent vs baseline. Flag a rising rate as a reliability regression. Name the tools whose gap grew most.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 65 lines · 73 tokens per session scan A 22391c839b09
regression-alert is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 3d ago), licensed MIT. It adds 73 tokens to every session and 889 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
code-remediate
Apply selected review fixes; bare PR targets use current online items, while PR +review adds the latest matching artifact.
nodejs-expert
Expert-level Node.js backend development with Express, async patterns, streams, performance optimization, and production best practices. Use when the user mentions JavaScript, backend, Express, or async, or when the task involves Modern Node.js Features, Express Framework, File System Operations, or HTTP Requests.
assess
Analyze issue/PR/problem before implementation; produce source-backed findings and measurable gates.
optimize
Optimize a measurable metric with bounded iterations, guardrails, and regression gates.
react-tanstack-router
Use when implementing routing in a React app (NOT Next.js) with TanStack Router — file-based routes, loaders, search params.
laravel-blade
Create Blade templates with components, slots, layouts, and directives. Use when building views, reusable components, or templating.