When fast-agent sessions go sideways, this is your forensics kit. It walks you through the session directory structure, shows you how to parse session.json and history files, and gives you jq commands to correlate tool calls with results, track timing across LLM and tool invocations, and spot common failure patterns like unanswered tool calls or duplicate user messages. The real value is in the investigation recipes: finding tool loops, calculating session statistics, matching sub-agent traces to main sessions via monotonic clock values. If you've ever stared at a 300-message history wondering where things went wrong, these jq snippets will save you an hour of manual JSON archaeology.
npx -y skills add evalstate/fast-agent --skill session-investigator --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
cursor/plugins
metabase/metabase
metabase/metabase
telagod/code-abyss
github/awesome-copilot
DietrichGebert/ponytail