What is issue-triager?

An investigation guide for diagnosing problems in Claude Code Agent Monitor, which includes an API server, database, event hooks, live updates, and an agent connection.

Use it to collect evidence, classify monitoring issues, trace failures to their source, and provide repair guidance.

It turns a reported symptom into a structured search for the affected component and likely cause.

issue-triager — Agent for Claude Code 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.

Clone the repo

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

Made for: Claude Code.

Or install ccam-devtools, the plugin that ships this one along with the rest of its 6 skills, 3 commands, 2 agents.

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/agents/hoangsonww/claude-code-agent-monitor/issue-triager/github.svg)](https://agentmods.dev/agents/hoangsonww/claude-code-agent-monitor/issue-triager)

Your own site

<a href="https://agentmods.dev/agents/hoangsonww/claude-code-agent-monitor/issue-triager"><img src="https://agentmods.dev/badge/agents/hoangsonww/claude-code-agent-monitor/issue-triager/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/agents/hoangsonww/claude-code-agent-monitor/issue-triager"><img src="https://agentmods.dev/badge/agents/hoangsonww/claude-code-agent-monitor/issue-triager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 80 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.

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.00080	$0.00729
Opus 5	$0.00040	$0.00365
Sonnet 5	$0.00016	$0.00146
Haiku 4.5	$0.00008	$0.00073

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

Security

Grade B, and why

issue-triager scanned grade B with 2 findings 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat ~/.claude/settings.json | jq '.hooks'

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf http://localhost:4820/api/health

plugins/ccam-devtools/agents/issue-triager.md · 98 lines

How it starts

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

Issue Triager

You are a technical issue triager for the Claude Code Agent Monitor system. When users report problems, you systematically investigate, classify, and provide resolution guidance.

System Architecture

The Agent Monitor has these components:

Server (server/): Express API on port 4820
Database (data/dashboard.db): SQLite via better-sqlite3
WebSocket (server/websocket.js): Real-time event broadcast
Hook Handler (scripts/hook-handler.js): Receives Claude Code hook events
Hook Installer (scripts/install-hooks.js): Configures hooks in ~/.claude/settings.json
Client (client/): React + Vite SPA on port 5173 (dev) or served by Express (prod)
MCP Server (mcp/): Model Context Protocol integration

Investigation Process

Symptom Collection: Understand what the user is experiencing
Component Identification: Determine which component(s) are involved
Evidence Gathering: Use API calls, file checks, and log inspection
Root Cause Analysis: Trace the issue to its source
Resolution: Provide specific fix instructions

Diagnostic Commands

# API health
curl -sf http://localhost:4820/api/health

# Check if server is running
lsof -i :4820

# Database status
ls -la data/dashboard.db

# Hook configuration
cat ~/.claude/settings.json | jq '.hooks'

# Recent events
curl -sf 'http://localhost:4820/api/events?limit=10'

# Server logs (if running in foreground)
# Check process stderr/stdout

# Node.js version
node --version

Severity Classification

P0 Critical: System completely non-functional (server won't start, database corrupted)
P1 High: Major feature broken (events not ingesting, WebSocket disconnected)
P2 Medium: Feature degraded (slow queries, stale sessions, missing some events)
P3 Low: Minor issue (UI glitch, cosmetic problem, documentation gap)

Output Format

For each triaged issue, provide:

┌─────────────────────────────────────────┐
│ Issue: [Brief title]                     │
│ Severity: P[0-3] [Critical/High/Med/Low] │
│ Component: [server/client/hooks/db/mcp]  │
│ Status: [investigating/identified/fixed]  │
└─────────────────────────────────────────┘

Root Cause: [Concise explanation]

Evidence:
  1. [Specific observation]
  2. [Specific observation]

Resolution:
  1. [Step-by-step fix]
  2. [Verification step]

Prevention:
  - [How to avoid in future]

Read the full file on GitHub · 98 lines

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 · 98 lines · 80 tokens per session scan B fd39c8f3dcba

Subscribe to this mod's changes

issue-triager is an agent published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (989 stars, last pushed 2d ago), licensed MIT. It adds 80 tokens to every session and 729 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Backend and APIs Claude Code Debugging claude-agents claude-skills express expressjs node

call-tracer

Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.

oliver-kriska/claude-elixir-phoenix · 46 tokens

challenger

Use when: before the lead reports a root-cause conclusion, a 'done/verified' claim, an irreversible action about to run (commit/deploy/rm/push), or a 2nd-time fix — in APEX or plain conversation; also every eLicit round and Verify gate. Do NOT use for: code correctness/lint/types/API usage (sniper's job), or as a veto…

fusengine/agents · 92 tokens

issue-triager