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 event-tracegit 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/event-trace)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/event-trace"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/event-trace/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/event-trace"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/event-trace.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.00073 | $0.00808 |
| Opus 5 | $0.00036 | $0.00404 |
| Sonnet 5 | $0.00015 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
event-trace 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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Trace
Build a chronological, annotated event timeline for a single session.
Input
The user provides: $ARGUMENTS
This is a session ID. It may also be:
latest/last— trace the most recently updated sessionerrors— trace the most recent session whose status iserror
Data Sources
| Endpoint | Returns |
|---|---|
GET /api/sessions?limit=N |
session list (used to resolve latest/errors and the target id) |
GET /api/sessions/:id |
full session detail (status, model, cwd, started_at, ended_at, cost, nested agents + events) |
GET /api/events?session_id=X |
the ordered event stream: event_type, tool_name, summary, data, timestamp |
Report Sections
1. Resolve the session
If $ARGUMENTS is a raw id, use it. If latest/last, call
GET /api/sessions?limit=1. If errors, call
GET /api/sessions?limit=10&status=error and pick the newest. Confirm the id
resolves via GET /api/sessions/:id; if not, report it as missing and stop.
2. Session header
From GET /api/sessions/:id: id, status, model, cwd, started_at → ended_at,
total duration, cost (USD to 4 decimals), and counts (events, agents).
3. Ordered timeline
From GET /api/events?session_id=X, list every event in timestamp order. One row
per event:
| # | time | Δ since prev | event_type | tool_name | summary |
Cover all event types present: SessionStart, PreToolUse, PostToolUse, Stop, SubagentStop, Compaction, APIError, TurnDuration, Notification, SessionEnd.
4. Gap & failure highlights
Annotate the timeline:
- Gaps: any Δ > 30s between consecutive events — mark ⏳ and note the wait.
- Unpaired tool calls: a PreToolUse with no matching PostToolUse (same tool_name, next in stream) — mark ⚠️ "no completion recorded".
- Failures: APIError events and PostToolUse whose
summary/dataindicates an error — mark ❌ with the error text. - Compaction: mark ♻️ and note it resets the visible token baseline.
- Missing bookends: no SessionStart at the head or no Stop/SessionEnd at the tail of an ended session — mark 🚩.
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.
- 9d ago First seen · 74 lines · 73 tokens per session scan A e2369483bb24
event-trace is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 4d ago), licensed MIT. It adds 73 tokens to every session and 808 once invoked, about $0.0004 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.
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.
qa-check
Auto-detects the project's tech stack, then audits for Accessibility, Performance, and Code Quality. Works across WordPress/PHP, Python, Node/JS, and static web projects.