An error scan that reviews recent coding-agent activity for API errors and tools that started but never reported completion. It groups the failures by tool and model.

Use it to scan all recent sessions, a selected number of sessions, one session, or only API or tool failures.

It turns scattered failure events into a ranked view of the most frequent problems and where they occur.

error-scan — Skill for Claude Code and Codex by hoangsonww

Install

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.

Any agent

npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill error-scan

Clone the repo

git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor

Made for: Claude Code, Codex.

Or install ccam-quality, the plugin that ships this one along with the rest of its 5 skills, 3 commands, 1 agent.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/error-scan/github.svg)](https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/error-scan)

Your own site

<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/error-scan"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/error-scan/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/error-scan"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/error-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 754 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00070	$0.00754
Opus 5	$0.00035	$0.00377
Sonnet 5	$0.00014	$0.00151
Haiku 4.5	$0.00007	$0.00075

Measured 7d ago against content hash 4242e051fadf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

error-scan 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 7d 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: only report what the API returns. If `curl` cannot reach `http://localhost:4820`, tell the user to start the dashboard with `npm start` from the repo root.

plugins/ccam-quality/skills/error-scan/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Error Scan

Sweep recent events across sessions for error and failure signals, then rank them by how often they occur and which tool or model produced them.

Input

The user provides: $ARGUMENTS

This may be:

empty or "all" — scan every failure signal (default)
"api" — APIError events only
"tools" — tool-failure gaps only
a number N — limit the scan to the most recent N sessions
a session ID — scan a single session

Data Sources

Endpoint	Returns
`GET /api/analytics`	`event_types` (counts per type incl. PreToolUse, PostToolUse, APIError), `tool_usage` (top 20), `daily_events` (365d) — fleet-wide failure baseline
`GET /api/events?session_id=X`	Per-session event stream: `event_type`, `tool_name`, `summary`, `data`, `timestamp` — locate `APIError` and unmatched `PreToolUse`
`GET /api/sessions?limit=N`	Sessions with `id`, `status`, `model`, `started_at` — pick the recent window and attribute failures to a model

Report Sections

1. Scope

Resolve $ARGUMENTS to a session set: pull GET /api/sessions?limit=N (default 50, ordered by started_at). Report how many sessions and what time span are covered.

2. Fleet Failure Counts

From GET /api/analytics event_types, report total APIError count and the PreToolUse→PostToolUse gap: gap = PreToolUse − PostToolUse (unmatched tool starts = likely failures). State both as raw counts and as a share of total_events.

3. Group by Tool

For each session in scope, pull GET /api/events?session_id=X. Match each PreToolUse to its following PostToolUse by tool_name; unmatched starts are failures. Aggregate failures and APIError events per tool_name. Rank tools by failure frequency (descending).

4. Group by Model

Join failures to the owning session's model (from GET /api/sessions). Rank models by APIError count and tool-failure count.

5. Top Offenders

List the single most failure-prone tool, the most error-prone model, and the session with the most failures, each with its exact count and one-line summary excerpt from a representative event.

Read the full file on GitHub · 59 lines

Files

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.

agents/openai.yaml 256 B

Changes

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.

7d ago First seen · 59 lines · 70 tokens per session scan A 4242e051fadf

Subscribe to this mod's changes

error-scan is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (989 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 754 once invoked, about $0.0003 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.

Analytics and metrics Claude Code Debugging claude-agents claude-skills express expressjs node

error-scan