How do I install the Agenttrace Session Audit skill?

Run npx skillmds add thedixitjain/agenttrace-session-audit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agenttrace Session Audit safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agenttrace Session Audit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agenttrace Session Audit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agenttrace Session Audit?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agenttrace Session Audit by thedixitjain

Name: Agenttrace Session Audit
Rating: 4.2 (5 reviews)
Author: thedixitjain

Agenttrace Session Audit

Audit local AI coding-agent sessions with agenttrace. Use when the user asks to inspect Claude Code, Codex CLI, Gemini CLI, Qwen Code, Cline, Aider, Cursor exports, Hermes Agent, OpenCode, OpenClaw, Pi, Oh My Pi, Kimi CLI, Copilot-style logs, or generic JSON/JSONL traces for cost, tokens, tool failures, latency, anomalies, health, diffs, or CI gates.

thedixitjain ecfde42 2.3 KB Updated Sep 8, 2026 2 repo stars

File contents

agenttrace Session Audit

Use this skill when session logs need an operational read: spend, token burn, cache use, tool failures, retry loops, latency, health, anomalies, and CI gate readiness.

Workflow

Prefer the installed agenttrace binary when it is available on PATH.
If the binary is not available and the current directory is the luoyuctl/agenttrace repository, use go run ./cmd/agenttrace.
Start with discovery unless the user gave a specific file or directory:

agenttrace --doctor
agenttrace --overview

For a fast human report, use Markdown:

agenttrace --overview -f markdown -o agenttrace-overview.md

For automation or CI, use JSON or health gates:

agenttrace --overview -f json -o agenttrace-overview.json
agenttrace --overview --fail-under-health 80 --fail-on-critical --max-tool-fail-rate 15

For a single recent session:

agenttrace --latest
agenttrace --latest -f json

For a specific export or session directory:

agenttrace path/to/session-or-export.json
agenttrace --overview -d path/to/session-dir

Report Focus

Lead with the highest-risk sessions and the reason they matter.
Call out token/cost waste, repeated tool failures, retry loops, long gaps, and low health scores.
When proposing a CI gate, include the exact agenttrace command and threshold.
If no sessions are detected, run agenttrace --doctor and report the detected agent directories and next step.

Guardrails

Treat prompts, code, and session contents as local/private data. Do not upload logs to external services.
Do not invent metrics. If a parser cannot infer cost, model, or latency, say which field is missing.
Do not overwrite user reports unless the user asked for that output path.

Source: hashgraph-online/awesome-codex-plugins → plugins/luoyuctl/agenttrace/skills/agenttrace-session-audit/SKILL.md

---name: agenttrace-session-auditdescription: Audit local AI coding-agent sessions with agenttrace. Use when the user asks to inspect Claude Code, Codex CLI, Gemini CLI, Qwen Code, Cline, Aider, Cursor exports, Hermes Agent, OpenCode, OpenClaw, Pi, Oh My Pi, Kimi CLI, Copilot-style logs, or generic JSON/JSONL traces for cost, tokens, tool failures, latency, anomalies, health, diffs, or CI gates.---# agenttrace Session AuditUse this skill when session logs need an operational read: spend, token burn, cache use, tool failures, retry loops, latency, health, anomalies, and CI gate readiness.## Workflow1. Prefer the installed `agenttrace` binary when it is available on `PATH`.2. If the binary is not available and the current directory is the `luoyuctl/agenttrace` repository, use `go run ./cmd/agenttrace`.3. Start with discovery unless the user gave a specific file or directory:```bashagenttrace --doctoragenttrace --overview```4. For a fast human report, use Markdown:```bashagenttrace --overview -f markdown -o agenttrace-overview.md```5. For automation or CI, use JSON or health gates:```bashagenttrace --overview -f json -o agenttrace-overview.jsonagenttrace --overview --fail-under-health 80 --fail-on-critical --max-tool-fail-rate 15```6. For a single recent session:```bashagenttrace --latestagenttrace --latest -f json```7. For a specific export or session directory:```bashagenttrace path/to/session-or-export.jsonagenttrace --overview -d path/to/session-dir```## Report Focus- Lead with the highest-risk sessions and the reason they matter.- Call out token/cost waste, repeated tool failures, retry loops, long gaps, and low health scores.- When proposing a CI gate, include the exact `agenttrace` command and threshold.- If no sessions are detected, run `agenttrace --doctor` and report the detected agent directories and next step.## Guardrails- Treat prompts, code, and session contents as local/private data. Do not upload logs to external services.- Do not invent metrics. If a parser cannot infer cost, model, or latency, say which field is missing.- Do not overwrite user reports unless the user asked for that output path.---**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/luoyuctl/agenttrace/skills/agenttrace-session-audit/SKILL.md`

Frequently asked questions