Install
$ agentstack add skill-hoangsonww-claude-code-agent-monitor-hook-diagnostics ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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:
# 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:
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:
# Verify handler exists and is executable
ls -la
# Syntax check
node --check
4. Event Delivery Test
Send a test event and verify it arrives:
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:
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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hoangsonww
- Source: hoangsonww/Claude-Code-Agent-Monitor
- License: MIT
- Homepage: https://hoangsonww.github.io/Claude-Code-Agent-Monitor/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.