session-report

Generate an interactive HTML report of Claude Code session token usage from local transcripts.

16|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SocialGouv/iterion --skill session-report-socialgouv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-report
Source: https://github.com/SocialGouv/iterion/tree/main/vendor/github.com/SocialGouv/claw-code-go/internal/tools/bundled_skills/session-report/skills/session-report
Command: npx skills add https://github.com/SocialGouv/iterion --skill session-report-socialgouv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claude Code usage data is scattered across thousands of JSONL transcript files in ~/.claude/projects, making it hard to see where tokens, cache misses, and subagent costs actually go. This Skill consolidates those transcripts into a single explorable HTML report with findings and optimization suggestions. ## Core Features & Use Cases - Transcript Analysis: Runs a bundled Node.js analyzer that deduplicates API calls, attributes tokens to projects, skills, subagent types, and individual prompts, and detects cache breaks over 100k uncached tokens. - Self-Contained HTML Report: Embeds the JSON analysis into a bundled template with sortable tables, block-char project bars, a per-day session timeline, and expandable prompt drill-downs. - Findings & Recommendations: Fills the report with 3-5 data-backed takeaways (waste, anomalies, healthy signals) and concrete optimization callouts tied to specific rows. - Use Case: After a heavy week of Claude Code usage, run the report to discover that one project consumed 41% of tokens across 3 sessions and that cache-hit rate dropped below 85%, then adjust your workflow accordingly. ## Quick Start Ask the AI to generate a session report of my Claude Code usage for the last 7 days and save it to the current directory.

Frequently Asked Questions about session-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze Claude Code token usage across sessions?▼

Run the bundled analyze-sessions.mjs script with Node.js against ~/.claude/projects transcripts. It outputs JSON summarizing tokens, cache rates, subagent calls, and top prompts, which the skill embeds into an interactive HTML report.

How to generate a usage report for a specific time range?▼

Pass a --since flag such as 24h, 30d, or an ISO date to the analyzer; the default window is the last 7 days. Omit --since entirely to analyze all-time usage across every transcript.

What data does the Claude Code session report include?▼

The report covers overall input/output tokens with cache-read percentage, per-project and per-skill breakdowns, subagent type statistics, cache breaks over 100k uncached tokens, the most expensive prompts, and a per-day session timeline.

Does the analyzer double-count tokens from resumed sessions?▼

No. The analyzer deduplicates entries globally by uuid so replayed history from resumed sessions is not double-counted, and it dedupes API calls by requestId keeping the final output_tokens value.

Why is my cache-hit rate low in the session report?▼

A cache-hit rate below 85% usually means frequent cache breaks, where single calls exceed 100k uncached input tokens. The report lists these breaks with transcript context so you can identify which prompts or subagents caused them.