analyzing-cc-sessions

analyzing-cc-sessions is a skill for Claude Code from vladolaru/claude-code-plugins. It costs 71 tokens per session (4,452 once invoked), scanned A, original, MIT.

A guide and set of tools for reading Claude Code session logs, which record conversations and tool activity as JSONL files.

In plain words
What is it for?
Use it to parse session files, investigate failed subagents, correlate dispatches with their work, and calculate metrics such as tokens, duration, and tool calls.
Why use it?
It helps you reconstruct what an AI coding session or subagent actually did instead of relying on a summary. It can reveal errors, wasted work, and behavior patterns.

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/jane/projects/my-app.

Part of the pirategoat-tools plugin — 22 skills shipped together

Good fit Use it to parse session files, investigate failed subagents, correlate dispatches with their work, and calculate metrics such as tokens, duration, and tool calls.

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 vladolaru/claude-code-plugins
Claude Code
/plugin install pirategoat-tools

Made for: Claude Code.

Or install pirategoat-tools, the plugin that ships this one along with the rest of its 22 skills.

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-cc-sessions

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/vladolaru/claude-code-plugins/analyzing-cc-sessions"><img src="https://agentmods.dev/badge/skills/vladolaru/claude-code-plugins/analyzing-cc-sessions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,452 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.00071 $0.04452
Opus 5.5 $0.00028 $0.01781
Sonnet 5.5 $0.00014 $0.00890
Haiku 4.5 $0.00007 $0.00445

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

Security

Grade A, and why

analyzing-cc-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 2mo 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.

plugins/pirategoat-tools/skills/analyzing-cc-sessions/SKILL.md · 427 lines

How it starts

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

Skill Directory

Resolve SKILL_DIR to the absolute directory containing this SKILL.md, as shown by the current host, before using any bundled path below. Before a shell command uses $SKILL_DIR, assign it in that command or replace it with the resolved path. It is not a host-exported environment variable.

Analyzing Claude Code Raw Sessions

Overview

Claude Code stores every conversation as JSONL transcripts — one JSON object per line. Main sessions track the full human-agent dialogue. Subagent dispatches get their own JSONL files. Large tool outputs are persisted separately as text files.

Core principle: Main session = orchestration log. Subagent files = the real work. Tool-results = the large payloads. Most analysis targets subagent behavior, not the main session.

When to Use

  • Analyzing what happened in a CC session (efficiency, behavior, errors)
  • Parsing subagent logs for tool call patterns or waste
  • Extracting metrics (tokens, duration, tool counts, findings)
  • Debugging why a subagent failed or produced poor results
  • Building or maintaining session analysis scripts
  • Correlating main session dispatches with subagent execution

Before You Start

Your goal Start here
Understand what happened in a session Main session JSONL → find Agent tool calls → follow to subagent files
Analyze a specific subagent's behavior Subagent JSONL directly ({session}/subagents/agent-{id}.jsonl)
Extract metrics across sessions Existing analysis scripts (see below)
Debug why a subagent failed Subagent JSONL → last assistant entry → check for errors in preceding tool results
Correlate main session ↔ subagent Main session Agent tool_use → progress entries with agentId → subagent file

Session Data Locations

Project Directory

Sessions are stored per-project at:

~/.claude/projects/{path-hash}/

The {path-hash} is the absolute project path with / replaced by -, leading - stripped:

Read the full file on GitHub · 427 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. 2mo ago Changed · -12 lines 1be36aebe6bb
  2. 2mo ago First seen · 439 lines · 71 tokens per session scan A 97e2e7851876

Subscribe to this mod's changes

analyzing-cc-sessions is a skill published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed 5d ago), licensed MIT. It adds 71 tokens to every session and 4,452 once invoked, about $0.0003 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-03.

Related

analyzing-cc-sessions compared with skills from other repositories

analyzing-cc-sessions next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
analyzing-cc-sessionsvladolaru/claude-code-pluginsSkill85d agoMITA71Claude Code
imagegenopenai/codexSkill135ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill100ktodayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill316k7d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code