Individual skill
agent-run-forensics
Use when asked why an agent did something, what a past session or run changed, whether tests really passed, or to verify a session summary. Answers from the recorded transcript, not memory, with trace_finder.py, trace_timeline.py and claim_checker.py.
engineering/skills/agent-run-forensics/SKILL.md
Source commit 9ef0c3c213932e645cc5cbeeb3c35c3a762a2437
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 29,534
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- anthropic-claude Repository topic
- claude-ai Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- claude-code-skills Repository topic
- ai-coding-agent Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- openai-codex Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,352 bytesSKILL.mdcore · 5,352 bytesassets/claims_example.txtdoc · 210 bytesassets/forensic_answer_template.mddoc · 754 bytesreferences/claim_verification.mddoc · 3,442 bytesreferences/recorded_vs_inferred.mddoc · 4,005 bytesreferences/trace_sources.mddoc · 3,927 bytesscripts/claim_checker.pyruns · 10,443 bytesscripts/trace_core.pyruns · 35,873 bytesscripts/trace_finder.pyruns · 7,308 bytesscripts/trace_timeline.pyruns · 14,611 bytes
Read excerpt
# Agent Run Forensics
> **Portability:** 3 stdlib Python CLIs and one hook. Read-only, no network, no model calls.
> Secrets in transcripts are redacted in every output, with no switch to turn that off.
Agents are confidently wrong about their own history. Asked "why did you change
config.yaml?", an agent answers from what it remembers, and memory drops the
parts that matter: the test run that failed, the file a `sed -i` one-liner
rewrote, the edit made after the last green run. The harness recorded all of it.
This skill makes the answer come from that recording.
**The rule: when a question is about something that already happened, read the trace before answering.**
## Workflow