agentmods.dev

trace-analysis

trace-analysis is a skill for Claude Code from ai-analyst-lab/ai-analyst. It costs 44 tokens per session (312 once invoked), scanned A, original, MIT.

An analysis-provenance guide that follows a claim back through its source, data snapshot, query, result, and run records. Provenance means the evidence showing where a result came from.

In plain words
What is it for?
Use it when someone asks where a number came from or when you need to verify the query and evidence behind an analytical claim.
Why use it?
It helps find missing evidence and query mistakes that can produce a plausible result while answering the wrong question. It checks details such as filters, time ranges, joins, and the data population.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

not rated 322repo +3 changed 1mo ago A scan 44 tokens original MIT

Good fit Use it when someone asks where a number came from or when you need to verify the query and evidence behind an analytical claim.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ai-analyst-lab/ai-analyst/trace-analysis
View source ↗ ai-analyst-lab/ai-analyst
Install

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.

Any agent
npx skills add ai-analyst-lab/ai-analyst --skill trace-analysis
Clone the repo
git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst

Made for: Claude Code.

Wrote 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.

agentmods badge for trace-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/trace-analysis/github.svg)](https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/trace-analysis)
Your own site
<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/trace-analysis"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/trace-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for trace-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/trace-analysis"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/trace-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00312
Opus 5.5 $0.00018 $0.00125
Sonnet 5.5 $0.00009 $0.00062
Haiku 4.5 $0.00004 $0.00031

Measured 1mo ago against content hash 3b023e936f60, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

trace-analysis 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 1mo 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.

.claude/skills/trace-analysis/SKILL.md · 30 lines

What it actually says

Trace one analysis

First invoke the trace skill so the machine-readable provenance record, lightweight receipt, and shareable HTML exist. Then review the claim through these records:

  1. The output states the claim.
  2. The receipt identifies the source, data snapshot, query, and artifacts.
  3. The trace records how the run unfolded.
  4. Logs record specific system and query events.
  5. The query and result provide execution evidence.

Use helpers.evals.trace.inspect_receipt on working/trace_receipt_<analysis_id>.json to identify missing fields and initial query risks. Then inspect the analytical details that code cannot infer from syntax alone: population, filters, time window, timezone, exclusions, grain, join cardinality, missingness, referential integrity, freshness, reconciliation, and whether the claim stays within the evidence.

For a query with a join and aggregate, test the grain directly. Compare the candidate total with a defensible reference query when one exists. A query that runs successfully may still answer the wrong question.

Save the written review beside the analysis. Report the review path and the HTML trace path together. Report missing evidence as missing. A complete receipt makes an analysis inspectable. It does not make the analysis correct.

Changes

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.

  1. 1mo ago Changed · +9 lines 3b023e936f60
  2. 1mo ago First seen · 21 lines · 44 tokens per session scan A 601c922b46a6

Subscribe to this mod's changes

trace-analysis is a skill published in the GitHub repository ai-analyst-lab/ai-analyst (322 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 312 once invoked, about $0.0002 per session on Opus 5.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-09-12.

Analytics and metrics
Related

trace-analysis compared with skills from other repositories

trace-analysis next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
trace-analysisai-analyst-lab/ai-analystSkill3221mo agoMITA44Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code