agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
npx skills add majiayu000/claude-skill-registry --skill agenttrace-session-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# agenttrace Session Audit ## Overview Use this skill to inspect local AI coding-agent sessions with [agenttrace](https://github.com/luoyuctl/agenttrace). It focuses on the process behind a run: token and cost spikes, tool failures, retry loops, latency gaps, anomalies, health scores, and session-to-session diffs. agenttrace is local-first and reads session logs from tools such as Claude Code, Codex CLI, Gemini CLI, Aider, Cursor exports, OpenCode, Qwen Code, Kimi, and generic JSON or JSONL traces. ## When to Use This Skill - Use when a user asks why an AI coding run was slow, expensive, shallow, or unreliable. - Use when reviewing local agent logs before retrying a failed or suspicious task. - Use when building a lightweight CI health gate for AI-assisted coding sessions. - Use when comparing two attempts and looking for changed tool paths, retries, or cost patterns. ## How It Works ### Step 1: Discover Available Sessions Prefer an installed `agenttrace` binary when it is available on `PATH`. If the current repository is `luoyuctl/agenttrace`, use `go run ./cmd/agenttrace` instead. ```bash agenttrace --doctor agenttrace --overview ``` If no sessions are detected, report the direct
- Overview
- When to Use This Skill
- How It Works
- Step 1: Discover Available Sessions
- Step 2: Produce a Human-Readable Audit
- Step 3: Inspect One Session or Directory
- Step 4: Compare Attempts When Semantics Matter
- Step 5: Add Automation Gates
- Examples
- Quick Local Review
- CI Health Check
- Best Practices
- Limitations
- Security & Safety Notes
agenttrace --doctor agenttrace --overview agenttrace --overview -f markdown -o agenttrace-overview.md agenttrace --latest agenttrace --latest -f json agenttrace path/to/session-or-export.json agenttrace --overview -d path/to/session-dir agenttrace --overview -f json -o agenttrace-overview.json agenttrace --overview --fail-under-health 80 --fail-on-critical --max-tool-fail-rate 15 agenttrace --overview --fail-under-health 80 --fail-on-critical
What does the agenttrace-session-audit skill do?
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill agenttrace-session-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.