Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/luoyuctl/agenttrace/agenttrace-session-auditnpx skills add luoyuctl/agenttrace --skill agenttrace-session-auditgit clone --depth 1 https://github.com/luoyuctl/agenttraceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/luoyuctl/agenttrace/agenttrace-session-audit)<a href="https://agentmods.dev/skills/luoyuctl/agenttrace/agenttrace-session-audit"><img src="https://agentmods.dev/badge/skills/luoyuctl/agenttrace/agenttrace-session-audit.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00099 | $0.00612 |
| Opus 5 | $0.00049 | $0.00306 |
| Sonnet 5 | $0.00020 | $0.00122 |
| Haiku 4.5 | $0.00010 | $0.00061 |
Grade A, and why
agenttrace-session-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
agenttracebinary when it is available onPATH. - If the binary is not available and the current directory is the
luoyuctl/agenttracerepository, usecargo run -q -p 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
agenttracecommand and threshold. - If no sessions are detected, run
agenttrace --doctorand report the detected agent directories and next step. - Report the session capability level (
Detailed,Aggregate, orLimited) before relying on latency or step evidence. - Treat Tool Steps as metadata-only evidence. Do not imply that Aggregate or Limited sources have a complete execution trace.
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 compare missing event-level evidence as zero latency or zero failures; mark it unavailable.
- Do not overwrite user reports unless the user asked for that output path.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 66 lines · 99 tokens per session scan A 745416b848c5
agenttrace-session-audit is a skill published in the GitHub repository luoyuctl/agenttrace (129 stars, last pushed 12d ago), licensed MIT. It adds 99 tokens to every session and 612 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
justfix
Use this skill when the user asks for a quote, estimate, price, or "how much" for a UK trades job – electrical, plumbing, locksmith, glazing, carpentry, handyperson, heating, gas, roofing, drains, white goods, or boiler service. Calls the JustFix Estimator MCP server to return a cost breakdown, scope summary, and a…
sync-awareness
Suggest syncing MCP server configurations or instruction files to other AI coding agents when the user is editing MCP settings (.claude.json, .mcp.json) or modifying CLAUDE.md files. Available commands: /sync, /sync-list, /sync-diff, /sync-instructions.
platform-api
Queries the Genesys Cloud Platform API schema for endpoint details, permissions, parameters, and response formats. Use when user asks about Genesys Cloud API endpoints (e.g., "/api/v2/assistants/queues"), API documentation, API permissions, schemas, capabilities, or when implementing Genesys Cloud operations.
timeline-report
Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.
smart-explore
Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.
bootstrap
This skill guides you through setting up your Agent Recall persona. It runs automatically on first use or when invoked with /bootstrap.