Agent skill · Audited from source

Hook Diagnostics

skill · hoangsonww/Claude-Code-Agent-MonitorMIT licenceAudited 16 Oct 2026 · source 1f059c400d07

★ 1,080pushed 4 days ago
✓SAFEGrade B · 89/100 · 16 Oct 2026 · 1f059c4
1,080repo stars · whole hoangsonww/Claude-Code-Agent-Monitor

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 1f059c400d07 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Diagnose Claude Code hook installation, delivery, and ingestion issues. Checks hook configuration, connectivity, event flow, and identifies common problems. Use when events are not appearing in the dashboard.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Hook Diagnostics (hoangsonww/Claude-Code-Agent-Monitor)”. Retrieved 16 Oct 2026. https://modelsatlas.com/skills/hoangsonww/hook-diagnostics

Trust audit

Audit 0.4.1 · source read 16 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 1f059c400d07 · 16 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publisherhoangsonww GitHub userOwner of the repository this skill is read from
  • Source folderhoangsonww/Claude-Code-Agent-Monitor/plugins/ccam-devtools/skills/hook-diagnosticsThe exact folder we audited
  • LicenceMITAs the repository states it
  • Commit pinned for this verdict1f059c400d07A new audit runs when the source changes
  • Repository statusNot archivedLast push 4 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Diagnose Claude Code hook installation, delivery, and ingestion issues. Checks hook configuration, connectivity, event flow, and identifies common problems. Use when events are not appearing in the dashboard.

---
name: hook-diagnostics
description: >
  Diagnose Claude Code hook installation, delivery, and ingestion issues.
  Checks hook configuration, connectivity, event flow, and identifies
  common problems. Use when events are not appearing in the dashboard.
---

# Hook Diagnostics

Diagnose hook integration issues between Claude Code and the Agent Monitor.

## Input

The user provides: **$ARGUMENTS**

This may be:
- "full" or empty (default: run all diagnostics)
- "install" to check hook installation only
- "connectivity" to check dashboard connectivity only
- "events" to check event delivery only

## Procedure

Run diagnostic checks in this order:

### 1. Hook Installation Check
Verify hooks are installed in Claude Code settings:

```bash
# Check if hooks exist in Claude Code settings
cat ~/.claude/settings.json | jq '.hooks // empty'
```

Verify:
- All 7 expected hook types are registered: `PreToolUse`, `PostToolUse`, `Stop`, `SubagentStop`, `Notification`, `SessionStart`, `SessionEnd`
- Hook commands point to the correct handler script path
- Handler script exists and is readable at the configured path

### 2. Dashboard Connectivity
Test that the dashboard API is reachable:

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

Verify:
- Dashboard responds with 200 OK
- Response includes expected health fields
- WebSocket endpoint is accessible

### 3. Hook Handler Validation
Check the hook handler script:

```bash
# Verify handler exists and is executable
ls -la <handler-path>
# Syntax check
node --check <handler-path>
```

### 4. Event Delivery Test
Send a test event and verify it arrives:

```bash
echo '{"hook_type":"test","session_id":"diag-test","data":{}}' | \
  curl -sf -X POST http://localhost:4820/api/hooks/event \
  -H 'Content-Type: application/json' -d @-
```

### 5. Database Check
Verify the database is writable and events are persisted:

```bash
curl -sf http://localhost:4820/api/stats
curl -sf http://localhost:4820/api/events?limit=5
```

### 6. Recent Event Flow
Check if events are flowing:
- Time since last event received
- Events received in last hour
- Any gaps in event delivery

## Output Format

Present as a diagnostic report with:
```
Hook Diagnostics Report
━━━━━━━━━━━━━━━━━━━━━━
✅ Hook Installation .............. PASS
✅ Dashboard Connectivity ......... PASS
✅ Handler Script ................. PASS
⚠️ Event Delivery ................ WARN (slow)
✅ Database ....................... PASS
❌ Recent Event Flow .............. FAIL (no events in 2h)
━━━━━━━━━━━━━━━━━━━━━━
Overall: 5/6 checks passed
```

For each failed or warning check, include:
- What was expected vs what was found
- Specific remediation steps
- Commands to fix the issue

Excerpt, first 2,702 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 1f059c4

Download folder ↗
git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor
git -C Claude-Code-Agent-Monitor checkout 1f059c400d07

The author documents no install command, so this uses the repository directly. Our verdict covers commit 1f059c400d07 only.

Works in which agents?

What its own text says, not a test

AgentStatusMore
Claude CodeMentioned in its text, not testedSkills for Claude Code · About Claude Code
“Mentioned” means the skill’s text names the agent. We have not run it there.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 1f059c400d07

README badge

For maintainers · shows the latest audit

ModelsAtlas: SAFE BMODELSATLASSAFE · B
[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/hoangsonww/hook-diagnostics/badge.svg)](https://modelsatlas.com/skills/hoangsonww/hook-diagnostics/)

The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.

Similar skills

Anomaly Alert✓SAFE

hoangsonww/Claude-Code-Agent-Monitor

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,…

★ 1.1kGrade B
Cost Breakdown✓SAFE

hoangsonww/Claude-Code-Agent-Monitor

Break down Claude Code costs using the Agent Monitor pricing engine. Shows per-model costs (input, output, cache_read, cache_write at $/Mtok rates), per-session costs, daily trends, and compaction baseline token…

★ 1.1kGrade B
Daily Standup✓SAFE

hoangsonww/Claude-Code-Agent-Monitor

Generate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity…

★ 1.1kGrade B
Dashboard Status✓SAFE

hoangsonww/Claude-Code-Agent-Monitor

Quick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, reads the redacted hook status returned by…

★ 1.1kGrade B
Data Export✓SAFE

hoangsonww/Claude-Code-Agent-Monitor

Export Claude Code session and analytics data in JSON, CSV, or Markdown formats. Supports exporting sessions, events, costs, and analytics for external analysis or reporting. Use for data backup or integration.

★ 1.1kGrade B
Debug Live Issue✓SAFE

hoangsonww/Claude-Code-Agent-Monitor

Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.

★ 1.1kGrade B

Add this badge to your README

[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/hoangsonww/hook-diagnostics/badge.svg)](https://modelsatlas.com/skills/hoangsonww/hook-diagnostics/)

Questions about Hook Diagnostics

What does the Hook Diagnostics skill do?
🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity, tool usage, and subagent orchestration, providing live analytics, a Kanban status board, status notifications, a cute buddy, &
Is Hook Diagnostics safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Hook Diagnostics access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Hook Diagnostics work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (1f059c400d07), read on 2026-10-16. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.