agentleFS
Sign inStart free
apappascsapappascs/claude-code-sessions/skills/session-stats/SKILL.md

session-stats

Skill2 starsChanged 26 days agoMITView on GitHub

Shows token usage, model distribution, turn count, duration, and tool usage for a Claude Code session. Use when the user asks about token usage, session cost, model breakdown, or says "session stats" or "how much did this session use".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user provides a session ID or path, use it directly.

    line 15
  2. Very specific:

    Use the path field from the first result.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Session Stats

Show detailed statistics for a single session.

Step 1: Resolve the session

If the user provides a session ID or path, use it directly. Otherwise, find the current session:

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts list --project "$(basename $(pwd))" --limit 1 --format json

Use the path field from the first result.

Step 2: Run the stats script

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-parser.ts stats <session-jsonl-path>

Step 3: Present results

The script outputs a JSON object. Present as a visual summary:

  • Duration and turns as headline stats
  • Token usage as a breakdown (input, output, cache read, cache create) with totals
  • Model distribution as a list showing which models were used and how many turns each
  • Tool usage as a ranked list (most used first)

Note: Cost estimation is not available. Report raw token counts and model names only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free