Skip to content

agenttrace Session Audit

Audit local AI coding-agent sessions for cost, tool failures, latency and health using agenttrace.

Stars
49,023
Licence
MIT
Files
1 file

What it does

Once installed, the agent can inspect logs from local AI coding tools (such as Claude Code, Codex CLI, Gemini CLI or Cursor exports) and explain why a run was slow, expensive, unreliable or shallow. It uses the separate agenttrace command-line tool to produce reports on token and cost spikes, repeated tool failures, retry loops, latency gaps and health scores, and can suggest comparing a run against a known-good attempt. The skill itself is guidance only; it does not include the agenttrace program, which must be installed separately.

Great for

  • Developers who want to understand why an AI coding agent run wasted time or money
  • Teams that want a simple CI check on AI-assisted coding sessions
  • People reviewing local agent logs before retrying a failed task

Skip it if

  • Production LLM application monitoring, where dedicated tools like Langfuse are more suitable (the skill itself points there)
  • Judging whether final code is correct: the skill states healthy trace metrics do not prove correctness, so tests and diff review are still needed
  • Environments where session logs contain sensitive data and uploading them to outside services is not approved

Try asking

  • “Audit my latest Claude Code session and tell me why it was so expensive.”
  • “Show me the tool failures and retry loops in the session logs in this folder.”
  • “Create a Markdown health report of my recent AI coding runs.”
  • “Add a CI check that fails if agent session health drops below 80.”
Step-by-step guide: how to use agenttrace Session AuditInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    agenttrace-session-audit.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip agenttrace-session-audit.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip agenttrace-session-audit.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Verify the installed agenttrace version and run --help first, since flags and supported adapters can change.
  • Specify the exact session or export file rather than relying on --latest, which may pick an unrelated run.
  • Start CI gates in reporting-only mode and tighten thresholds once you know your team's normal baseline.

What's inside

  • SKILL.md

Redistributed unmodified from sickn33/agentic-awesome-skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.