AGENT SKILL

agenttrace-session-audit

Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.

License 许可
MIT
最近更新
2026-10-22
Stars
★ 1
Forks
0

01 前言 Front Matter

name
agenttrace-session-audit
risk
safe
tags
[ "ai-coding", "observability", "cost-tracking", "session-analysis" ]
tools
[ "claude", "cursor", "gemini", "codex-cli" ]
author
luoyuctl
source
community
license
MIT
category
development
date_added
2026-05-10
description
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
source_repo
luoyuctl/agenttrace
source_type
community
license_source
https://github.com/luoyuctl/agenttrace/blob/master/LICENSE

03 SKILL.md 正文

agenttrace Session Audit

Overview

Use this skill to inspect local AI coding-agent sessions with 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.

agenttrace --doctor
agenttrace --overview

If no sessions are detected, report the directories checked by --doctor and ask for the exported session file or log directory.

Step 2: Produce a Human-Readable Audit

Use Markdown when the user wants a concise report they can inspect or share.

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

In the report, lead with the highest-risk sessions and explain why they matter: critical anomalies, repeated tool failures, token or cost waste, long latency gaps, low health scores, and suspiciously shallow sessions.

Step 3: Inspect One Session or Directory

Use the latest session for a quick check, or pass an explicit export path when the user provides one.

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

Step 4: Compare Attempts When Semantics Matter

Token and latency metrics can look healthy even when an agent confidently takes the wrong implementation path. When the risk is semantic drift, pair the trace audit with a diff against a previous or known-good attempt.

Look for:

  • changed files or commands that diverge from the intended task
  • missing tests or verification steps compared with the reference attempt
  • repeated edits around the same files without a clear reason
  • lower cost that came from skipping necessary exploration

Step 5: Add Automation Gates

For CI or repeatable team workflows, use JSON output or health thresholds.

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

Tune thresholds to the project. A strict gate is useful for critical workflows; a reporting-only command is better while the team is learning its baseline.

Examples

Quick Local Review

agenttrace --overview
agenttrace --latest

Use this after a long coding-agent run to decide whether the next prompt should split the task, avoid a failing tool path, add missing tests, or reset context.

CI Health Check

agenttrace --overview --fail-under-health 80 --fail-on-critical

Use this when agent session logs are available in CI and the team wants a simple guard against critical anomalies or unhealthy runs.

Best Practices

  • Start with --doctor when session discovery is uncertain.
  • Report missing fields plainly; do not invent cost, model, latency, or health data.
  • Treat prompts, code, and session contents as private local data.
  • Prefer JSON output for automation and Markdown output for human review.
  • Use trace metrics for process failures and diff/reference review for semantic drift.

Limitations

  • agenttrace can only analyze logs that are present locally or provided as exports.
  • Some agents do not expose enough fields to infer cost, model, cache use, or latency.
  • Healthy trace metrics do not prove the final code is correct; still run tests and review diffs.
  • CI gates should start as advisory until the team understands normal baseline behavior.

Security & Safety Notes

  • Do not upload private session logs to external services unless the user explicitly approves it.
  • Do not overwrite user reports unless they requested that exact output path.
  • Avoid printing secrets found in prompts, tool output, environment variables, or logs.

Common Pitfalls

  • Problem: No sessions are found. Solution: Run agenttrace --doctor, then point agenttrace at the exported file or log directory.

  • Problem: A run looks cheap and fast but produced the wrong refactor. Solution: Compare the session against a prior attempt or known-good diff; cost metrics alone will miss semantic drift.

  • Problem: CI fails too often after adding a health gate. Solution: Start with JSON or Markdown reporting, inspect normal baselines, then tighten thresholds gradually.

Related Skills

  • @langfuse - Use for production LLM application tracing and evaluation.
  • @observability-engineer - Use for broader service monitoring, SLOs, and incident workflows.

04 同仓库更多 Skills

Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

testing-best-practices

Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

tailwindcss-development

Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

laravel-best-practices

Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

infer-conventions

Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai/rules`, resolve mixed or conflicting patterns (e.g. "are we using Form Requests or inline validation?"), or onboard agents and teammates to "how we do things here". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai/rules` files by hand.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

inertia-react-development

Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using <Link>, <Form>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

deploying-to-cloud

Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.

★ 1