session-analyzer

session-analyzer is a skill for Claude Code from clafollett/lafollettlabs-claude-plugins. It costs 36 tokens per session (1,957 once invoked), scanned B, original, MIT.

A tool for reading and analyzing Claude Code session files, which are JSONL records of conversations and tool use.

In plain words
What is it for?
Use it to find sessions, extract readable transcripts, review token or tool statistics, and search past conversations for a topic.
Why use it?
It turns hard-to-read session logs into useful information about what happened, how long it took, which tools were used, and how tokens were spent.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/foo/repo.

Part of the session-analyzer plugin — 1 skill shipped together

Good fit Use it to find sessions, extract readable transcripts, review token or tool statistics, and search past conversations for a topic.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add clafollett/lafollettlabs-claude-plugins
Claude Code
/plugin install session-analyzer

Made for: Claude Code.

Or install session-analyzer, the plugin that ships this one along with the rest of its 1 skill.

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 session-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/skills/clafollett/lafollettlabs-claude-plugins/session-analyzer/github.svg)](https://agentmods.dev/skills/clafollett/lafollettlabs-claude-plugins/session-analyzer)
Your own site
<a href="https://agentmods.dev/skills/clafollett/lafollettlabs-claude-plugins/session-analyzer"><img src="https://agentmods.dev/badge/skills/clafollett/lafollettlabs-claude-plugins/session-analyzer/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 session-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/skills/clafollett/lafollettlabs-claude-plugins/session-analyzer"><img src="https://agentmods.dev/badge/skills/clafollett/lafollettlabs-claude-plugins/session-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,957 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00036 $0.01957
Opus 5 $0.00018 $0.00979
Sonnet 5 $0.00007 $0.00391
Haiku 4.5 $0.00004 $0.00196

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

Security

Grade B, and why

session-analyzer scanned grade B with 1 finding 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 10d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/session-analyzer.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

[ -z "$SA" ] && SA=$(find ~/.claude/skills -path "*/session-analyzer/scripts/session-analyzer.py" -print -quit 2>/dev/null)
plugins/session-analyzer/skills/session-analyzer/SKILL.md · 181 lines

How it starts

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

Session Analyzer

Parse, extract, and analyze Claude Code session JSONL files. Zero dependencies — Python 3.10+ only.

When to Use

  • User asks to analyze a Claude Code session (token usage, tool stats, duration)
  • User wants a readable conversation transcript from a session
  • User asks to find or list their sessions
  • User wants to review what happened in a prior session
  • User asks about cache hit rates, model usage, or session efficiency
  • User asks "find the session where we discussed X"

Session File Locations

Claude Code stores sessions as JSONL files:

  • Project sessions: ~/.claude/projects/{project-hash}/{session-id}.jsonl
  • Project hash format: absolute repo path with / replaced by - (e.g., /Users/foo/repo-Users-foo-repo)

Script Location

The CLI script is at scripts/session-analyzer.py relative to this SKILL.md file.

The plugin cache at ~/.claude/plugins/cache/ keeps multiple versions side-by-side. The canonical active version is recorded in ~/.claude/plugins/installed_plugins.json under the installPath field. Use it to resolve the correct script:

# Resolve via installed_plugins.json (canonical — always points to the active version)
SA=$(python3 -c "
import json, pathlib
data = json.loads((pathlib.Path.home() / '.claude/plugins/installed_plugins.json').read_text())
entry = data.get('plugins', {}).get('session-analyzer@lafollettlabs-claude-plugins', [{}])[0]
print(pathlib.Path(entry['installPath']) / 'skills/session-analyzer/scripts/session-analyzer.py')
" 2>/dev/null)

# Fallback for manual install (no version ambiguity)
[ -z "$SA" ] && SA=$(find ~/.claude/skills -path "*/session-analyzer/scripts/session-analyzer.py" -print -quit 2>/dev/null)

Argument Hints — User Intent to Flags

When the user asks something fuzzy, map their intent to the right command and flags:

User says Command
"analyze my last session" list --latest -p <cwd> → pipe path to analyze
"show yesterday's sessions" list --since yesterday -p <cwd>
"the big session" / "longest session" list --min-size 5M -p <cwd>
"sessions this week" list --since 7d -p <cwd>
"find where we discussed CREW" search "CREW" -p <cwd>
"what did we talk about on Monday?" list --since 2026-04-21 --before 2026-04-22 -p <cwd>
"extract the full conversation" extract <path> (saves to temp, prints clickable path)
"export to my docs folder" extract <path> -o ~/Documents/
"show me the beginning" extract <path> --head 10 (stdout preview)
"what was the last thing?" extract <path> --tail 5 (stdout preview)
"show me with tool calls" extract <path> --tools --timestamps
"how many tokens did we use?" analyze <path>
"give me the JSON" list --json / analyze --format json

Read the full file on GitHub · 181 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 181 lines · 36 tokens per session scan B 64e851d6f039

Subscribe to this mod's changes

session-analyzer is a skill published in the GitHub repository clafollett/lafollettlabs-claude-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,957 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). 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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens