analyzing-claude-sessions

analyzing-claude-sessions is a skill for Claude Code, Codex from karashiiro/agent-skills. It costs 41 tokens per session (1,842 once invoked), scanned A, original, Unlicense.

A guide for reading Claude Code session logs, which are line-by-line records of conversations and tool activity, with command-line queries.

In plain words
What is it for?
Use it to inspect session messages, find recent sessions, examine subagents, or extract usage details from JSONL logs.
Why use it?
It makes it easier to investigate agent behavior, errors, performance, and tool use across saved sessions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions subagents; positional $N argument.

Good fit Use it to inspect session messages, find recent sessions, examine subagents, or extract usage details from JSONL logs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/karashiiro/agent-skills/analyzing-claude-sessions
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 karashiiro/agent-skills --skill analyzing-claude-sessions
Clone the repo
git clone --depth 1 https://github.com/karashiiro/agent-skills

Made for: Claude Code, Codex.

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 analyzing-claude-sessions

README.md
[![agentmods](https://agentmods.dev/badge/skills/karashiiro/agent-skills/analyzing-claude-sessions/github.svg)](https://agentmods.dev/skills/karashiiro/agent-skills/analyzing-claude-sessions)
Your own site
<a href="https://agentmods.dev/skills/karashiiro/agent-skills/analyzing-claude-sessions"><img src="https://agentmods.dev/badge/skills/karashiiro/agent-skills/analyzing-claude-sessions/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 analyzing-claude-sessions

Your own site · 80×15
<a href="https://agentmods.dev/skills/karashiiro/agent-skills/analyzing-claude-sessions"><img src="https://agentmods.dev/badge/skills/karashiiro/agent-skills/analyzing-claude-sessions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,842 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.00041 $0.01842
Opus 5 $0.00020 $0.00921
Sonnet 5 $0.00008 $0.00368
Haiku 4.5 $0.00004 $0.00184

Measured 12d ago against content hash 10fb1ccf36ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

analyzing-claude-sessions 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 12d 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.

analyzing-claude-sessions/SKILL.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyzing Claude Code Session Logs

Extract insights from Claude Code session transcripts using jq. Session logs are JSONL files where each line is a message in the conversation.

Log Locations

Log Type Path
Main session ~/.claude/projects/{project-hash}/{session-id}.jsonl
Subagent ~/.claude/projects/{project-hash}/{session-id}/subagents/agent-{agent-id}.jsonl
Tool results ~/.claude/projects/{project-hash}/{session-id}/tool-results/

Find the most recent session:

ls -t ~/.claude/projects/*/*.jsonl | head -1

List subagents for a session:

ls ~/.claude/projects/{project-hash}/{session-id}/subagents/

Message Structure

Each JSONL line has this shape:

{
  "type": "user|assistant|progress|system|file-history-snapshot",
  "message": {
    "role": "user|assistant",
    "content": "string" | [{"type": "text|tool_use|tool_result", ...}],
    "model": "claude-sonnet-4-5-...",
    "usage": {"input_tokens": N, "output_tokens": N, ...},
    "stop_reason": "end_turn|tool_use|..."
  },
  "timestamp": "ISO8601",
  "uuid": "...",
  "agentId": "...",
  "sessionId": "..."
}

Assistant messages have content as an array of blocks:

  • {"type": "text", "text": "..."} — text output
  • {"type": "tool_use", "name": "Read", "id": "toolu_...", "input": {...}} — tool call
  • {"type": "tool_result", "tool_use_id": "toolu_...", "content": "...", "is_error": bool} — tool response

Shell Quoting Note

jq filters work fine inline as long as the file path is either a literal or expanded in the same && chain as the variable assignment. The select(.type == "tool_use") syntax with inner double quotes works correctly inside single-quoted jq filters.

For array content blocks, use the if type == "array" guard since user messages have string content:

jq -r '.message.content | if type == "array" then [.[] | select(.type == "tool_use") | .name] | .[] else empty end' session.jsonl

For loops over subagent files, assign the directory path first:

SUBS="path/to/subagents" && for f in "$SUBS"/agent-*.jsonl; do
  jq -r '...' "$f"
done

Read the full file on GitHub · 172 lines

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. 12d ago First seen · 172 lines · 41 tokens per session scan A 10fb1ccf36ca

Subscribe to this mod's changes

analyzing-claude-sessions is a skill published in the GitHub repository karashiiro/agent-skills (2 stars, last pushed 4mo ago), licensed Unlicense. It adds 41 tokens to every session and 1,842 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens