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-timelinegit 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-timeline)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/session-timeline"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/session-timeline/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-timeline"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/session-timeline.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.00071 | $0.00673 |
| Opus 5 | $0.00036 | $0.00336 |
| Sonnet 5 | $0.00014 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
session-timeline 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Timeline
Reconstruct the chronological event timeline of a single Claude Code session.
Input
The user provides: $ARGUMENTS
- A session ID to time-line, or
- "latest" / "last" for the most recent session.
Data Sources
| Endpoint | Returns |
|---|---|
GET /api/sessions/:id |
session header: status, model, cwd, started_at, ended_at, cost, metadata (thinking_blocks, turn_count, total_turn_duration_ms) — and nested events |
GET /api/events?session_id=X |
the full event stream: event_type (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, Notification, Compaction, APIError, TurnDuration), tool_name, summary, data, timestamp |
Report Sections
1. Resolve & header
If "latest", GET /api/sessions?limit=1 to get the id, then GET /api/sessions/:id.
Print a one-line header: id, status, model, cwd basename, started_at → ended_at,
turn_count, total_turn_duration_ms, cost.
2. Build the ordered timeline
GET /api/events?session_id=X. Sort strictly by timestamp. For each event emit a
row with: relative offset from started_at (e.g. +00:03.412), event_type,
tool_name (when present), and a one-line summary.
3. Compute durations
Pair each PreToolUse with its matching PostToolUse (same tool_name, next
occurrence) and show the tool's wall-clock duration. For TurnDuration events use
the recorded duration directly. Flag any PreToolUse with no matching PostToolUse
as unclosed.
4. Annotate notable points
Mark APIError (❌), Compaction (⚠️ context compressed), SubagentStop
(subagent finished), Notification (ℹ️), and any timeline gap > 30s between
consecutive events as an idle window.
5. Tallies
Event count by type, total tool time vs. session wall time, and the longest single tool call.
Output
A Markdown table — offset | event_type | tool_name | duration | summary — in
strict timestamp order, preceded by the header line and followed by the tallies.
Durations in ms or mm:ss.mmm; currency as USD to 4 decimal places. Never invent a
duration when a PostToolUse is missing — label it unclosed. If the dashboard is
unreachable, tell the user to start it with npm start from the repo root.
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 · 63 lines · 71 tokens per session scan A b46c7ab4990a
session-timeline is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 4d ago), licensed MIT. It adds 71 tokens to every session and 673 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.