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 session-debuggit 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/session-debug)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/session-debug"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/session-debug/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/session-debug"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/session-debug.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.00092 | $0.00682 |
| Opus 5 | $0.00046 | $0.00341 |
| Sonnet 5 | $0.00018 | $0.00136 |
| Haiku 4.5 | $0.00009 | $0.00068 |
Grade A, and why
session-debug scanned grade A with 0 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 6d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Debug
Debug and inspect a Claude Code session from Agent Monitor data.
Input
The user provides: $ARGUMENTS
This may be:
- A session ID to debug
- "latest" or "last" for the most recent session
- "errors" to find and debug the most recent errored session
Procedure
-
Identify the target session:
- If session ID given:
GET /api/sessions/{id}fromhttp://localhost:4820 - If "latest":
GET /api/sessions?limit=1(default sort: most recently updated first) - If "errors":
GET /api/sessions?limit=10&status=error
- If session ID given:
-
Collect full session data:
- Session metadata: status, model, cwd, timestamps, duration
- Events:
GET /api/events?session_id={session_id}— full event timeline - Agents:
GET /api/agents?session_id={session_id}— all agents in session - Cost:
GET /api/pricing/cost/{session_id}
-
Analyze the session:
Session Lifecycle
- Start time → first event → last event → end time
- Status transitions (active → working → completed/error)
- Total duration and active-vs-idle time
Event Chain Analysis
- Chronological event list with timestamps and durations
- Identify the critical path (longest chain of dependent events)
- Flag events that took unusually long
- Highlight error events with full error context
Agent Inspection
- List all agents: type, task, status, duration
- Subagent tree visualization (parent → children)
- Agents that failed and their last known state
- Agent switching patterns (when and why new agents spawned)
Tool Execution Trace
- Every tool invocation in order with: tool name, duration, success/failure
- Failed tool calls with error messages
- Tool retry patterns (same tool called multiple times)
Anomaly Detection
- Events out of expected order
- Gaps in event timeline (>30s with no events)
- Duplicate events or agent states
- Token usage spikes (compaction indicators)
-
Diagnosis:
- Root cause hypothesis (if errors present)
- Contributing factors
- Remediation suggestions
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.
- 6d ago First seen · 80 lines · 92 tokens per session scan A 0589cebc893c
session-debug is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (987 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 682 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. 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.
change-analysis
Analyze issue/PR/problem before implementation; produce source-backed findings and measurable gates.
php-quality-tooling
Use when setting up PHPStan, Rector, or PHP-CS-Fixer on a non-Laravel PHP project, incl. CI wiring. Do NOT use for Laravel (Pint/Larastan), tests, or syntax.
breaking-changes
Use when checking whether a Claude Code update breaks our plugin ecosystem — hooks, agent frontmatter, manifest schema, or skill format.
radin-doctor
Check that radin's own install under /.claude is complete and its optional companion tools are reachable. Use for /radin-doctor, "check my radin install", "is radin installed correctly", "radin doctor", "verify radin install".
systematic-debugging
Guides root cause investigation before proposing fixes. Use when debugging, diagnosing failures, investigating test errors, or tracing unexpected behaviour.