Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Trace the full event chain for one Claude Code session into an ordered timeline of every event type with toolname and summary, highlighting gaps, out-of-order events, and failures.
Install Event Trace
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor event-trace --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ccam-devtools/skills/event-trace .claude/skills/event-trace && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "event-trace" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-devtools/skills/event-trace into .claude/skills/event-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-trace", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-devtools/skills/event-traceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor event-trace --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ccam-devtools/skills/event-trace .agents/skills/event-trace && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "event-trace" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-devtools/skills/event-trace into .agents/skills/event-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-trace", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor event-trace --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ccam-devtools/skills/event-trace .cursor/skills/event-trace && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "event-trace" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-devtools/skills/event-trace into .cursor/skills/event-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-trace", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git --path plugins/ccam-devtools/skills/event-trace--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor event-trace --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ccam-devtools/skills/event-trace .gemini/skills/event-trace && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "event-trace" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-devtools/skills/event-trace into .gemini/skills/event-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-trace", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor event-traceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ccam-devtools/skills/event-trace .github/skills/event-trace && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "event-trace" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-devtools/skills/event-trace into .github/skills/event-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-trace", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor event-trace --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ccam-devtools/skills/event-trace .opencode/skills/event-trace && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "event-trace" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-devtools/skills/event-trace into .opencode/skills/event-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-trace", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
event-trace- GitHub stars
- 1.1k
- Token cost
- ~759 tokens
- SKILL.md length
- 352 words
- Files
- 2
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- MIT
At a glance
Trace the full event chain for one Claude Code session into an ordered timeline of every event type with toolname and summary, highlighting gaps, out-of-order events, and failures.
- Works in 5 steps: Resolve the session → Session header → Ordered timeline → …
- Debugging what a session actually did
- SKILL.md covers Input, Data Sources, Report Sections and Output
- Calls npm
What it does
Event Trace is an agent skill from hoangsonww/Claude-Code-Agent-Monitor. Trace the full event chain for one Claude Code session into an ordered timeline of every event type with toolname and summary, highlighting gaps, out-of-order events, and failures. Reads /api/events?sessionid= and /api/sessions/:id from the Agent Monitor dashboard. Use when debugging what a session actually did, step by step.
Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development. The repository describes itself as: 🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity… The licence is MIT.
When your agent uses it
- Debugging what a session actually did
Example prompts
- “/event-trace”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1a10d68. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Event Trace loads about 759 tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 352 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hoangsonww/Claude-Code-Agent-Monitor at commit 1a10d68, republished under its MIT licence (© hoangsonww). 352 words, ~759 tokens.
Download SKILL.mdSave it as
.claude/skills/event-trace/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- event-trace
- description
- Trace the full event chain for one Claude Code session into an ordered timeline of every event type with tool_name and summary, highlighting gaps, out-of-order events, and failures. Reads /api/events?session_id= and /api/sessions/:id from the Agent Monitor dashboard. Use when debugging what a session actually did, step by step.
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.
Show full SKILL.md (163 more words)Show less
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 🚩.
5. Verdict
One line: CLEAN, GAPS DETECTED, or FAILURES PRESENT — with the count of each flag type and the single most likely thing to investigate next.
Output
- Markdown timeline table, events in strict timestamp order.
- Status glyphs inline: ✅ ok, ❌ error, ⚠️ warning/unpaired, ⏳ gap, ♻️ compaction, 🚩 missing bookend.
- Currency in USD to 4 decimals.
- Cite only event data returned by the API — do not invent timestamps or summaries.
- If the dashboard is unreachable, tell the user to start it with
npm startfrom the repo root.
© hoangsonww, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in plugins/ccam-devtools/skills/event-trace of hoangsonww/Claude-Code-Agent-Monitor.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 1a10d68
Compare with similar skills
Event Trace next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Event Trace this skillhoangsonww/Claude-Code-Agent-Monitor | 1.1k | — | ~759 | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from hoangsonww/Claude-Code-Agent-Monitor
All 78 skills in this repoVersion Release
hoangsonww/Claude-Code-Agent-Monitor
Choose and apply the correct semantic version bump for this repository.
Budget Set
hoangsonww/Claude-Code-Agent-Monitor
Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard.
Cache Efficiency
hoangsonww/Claude-Code-Agent-Monitor
Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (totalcacheread / (totalcacheread + totalinput)), cachewrite vs cacheread reuse, cache-read…
Cost Breakdown
hoangsonww/Claude-Code-Agent-Monitor
Break down Claude Code costs using the Agent Monitor pricing engine.
Dag Map
hoangsonww/Claude-Code-Agent-Monitor
Render the multi-agent orchestration DAG for a session — parent→child subagent edges, tree depth, and fan-out — from the Agent Monitor workflow intelligence API.
Dashboard Status
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…
Related
Categories
Questions about Event Trace
What does Event Trace do?
Trace the full event chain for one Claude Code session into an ordered timeline of every event type with toolname and summary, highlighting gaps, out-of-order events, and failures. Event Trace is an agent skill from hoangsonww/Claude-Code-Agent-Monitor. Trace the full event chain for one Claude Code session into an ordered timeline of every event type with toolname and summary, highlighting gaps, out-of-order events, and failures.
When should I use Event Trace?
Event Trace fits situations like: debugging what a session actually did.
How do I install Event Trace in Claude Code?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace -a claude-code`. Or copy the skill folder (plugins/ccam-devtools/skills/event-trace in hoangsonww/Claude-Code-Agent-Monitor) into .claude/skills/event-trace in your project. Claude Code loads it when a task matches its description.
How do I install Event Trace in Codex?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace -a codex`. Or copy the skill folder (plugins/ccam-devtools/skills/event-trace in hoangsonww/Claude-Code-Agent-Monitor) into .agents/skills/event-trace in your project. Codex loads it when a task matches its description.
Can I use Event Trace in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/event-trace, .gemini/skills/event-trace, .github/skills/event-trace and .opencode/skills/event-trace in your project.
What does Event Trace need to run?
Going by SKILL.md and its folder, Event Trace needs the command-line tools its instructions call (npm).
Does Event Trace access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Event Trace safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Event Trace use?
Event Trace is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Event Trace use?
About 759 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Event Trace?
Skills that share tags, products or a category with Event Trace: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Event Trace?
hoangsonww (a GitHub user) maintains it in hoangsonww/Claude-Code-Agent-Monitor, which has 1,054 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 8, 2026.
Source: hoangsonww/Claude-Code-Agent-Monitor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.