A command that runs an automated analysis of Claude Code session transcripts and writes structured findings about workflow problems and improvement opportunities.

Use it to analyze a project's sessions across selected dimensions such as errors, tooling gaps, interruptions, delegation, or workflow detours.

It saves you from manually reviewing many session records to find recurring errors, tool misuse, delegation issues, or missing safeguards.

analyze — Command for Claude Code by Jamie-BitFlight/claude

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.

Clone the repo

git clone --depth 1 https://github.com/Jamie-BitFlight/claude_skills

Made for: Claude Code.

Or install agentskill-kaizen, the plugin that ships this one along with the rest of its 4 skills, 4 commands, 2 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jamie-bitflight/claude_skills/analyze/github.svg)](https://agentmods.dev/commands/jamie-bitflight/claude_skills/analyze)

Your own site

<a href="https://agentmods.dev/commands/jamie-bitflight/claude_skills/analyze"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/claude_skills/analyze/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jamie-bitflight/claude_skills/analyze"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/claude_skills/analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 445 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.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.00445
Opus 5.5	$0.00004	$0.00178
Sonnet 5.5	$0.00002	$0.00089
Haiku 4.5	$0.00001	$0.00044

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

Security

Grade A, and why

analyze 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/agentskill-kaizen/commands/analyze.md · 45 lines

What it actually says

Run the autonomous transcript analysis pipeline. Spawn the @transcript-analyst agent to query JSONL session data, detect anti-patterns, and write structured findings.

Arguments

<user_arguments>$ARGUMENTS</user_arguments>

--project {project} — Scope analysis to a specific project. The project key is the path with hyphens replacing slashes. Default: current project (derived from cwd).
--dimensions {dimensions} — Comma-separated list of dimensions to analyze. Options: tool-misuse, errors, tooling-gaps, delegation, shortest-path, red-herrings, interruptions, missing-hooks, all. Default: all.

Execution Steps

Resolve transcript path. Determine the project transcript directory:
```
~/.claude/projects/{project}/
```
If --project is provided, use it as the project key. Otherwise, derive from the current working directory by replacing / with - and prepending -.
Create output directory. Ensure .planning/kaizen/ exists in the current project root.

Delegate the analysis via Agent tool:

subagent_type: agentskill-kaizen:transcript-analyst
prompt: "Analyze transcripts at {path}. Dimensions: {dimensions}. Write findings to .planning/kaizen/analysis-{date}.md"

The agent has access to DuckDB MCP for SQL queries and the custom kaizen MCP for process mining. Let it choose its own analysis approach.

Report results. After the agent completes, summarize:
- Number of sessions analyzed
- Number of findings by severity
- Path to the analysis report file

Output

Analysis report written to .planning/kaizen/analysis-{YYYY-MM-DD}.md with structured findings including session IDs, severity, evidence, and improvement recommendations.

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.

2mo ago First seen · 45 lines · 10 tokens per session scan A 5a367d60aba2

Subscribe to this mod's changes

analyze is a command published in the GitHub repository Jamie-BitFlight/claude_skills (67 stars, last pushed 19d ago), licensed MIT. It adds 10 tokens to every session and 445 once invoked, about $0.0000 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.

Analytics and metrics Building agents

analyze next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
analyzeJamie-BitFlight/claude_skills	Command	67	19d ago	MIT	A	10	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code