session-detail
Skill2 starsChanged 27 days agoMITView on GitHub
Show detailed information about a Claude Code session including stats, token usage, models used, tools called, associated tasks, and conversation messages. Use when the user says "show session", "session details", "what happened in session X".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- thebpandey/session-detailtheir own version, first seen Oct 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- thebpandey/session-detail★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- session-cleanupSkill
- session-deleteSkill
- session-diffSkill
- session-exportSkill
- session-listSkill
- session-memory-auditSkill
- session-memory-searchSkill
- session-memorySkill
- session-resumeSkill
- session-searchSkill
- session-statsSkill
- session-tasksSkill
- session-timelineSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
If the user wants to see the conversation:
≈ “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.
Files
Session Detail
Show comprehensive details about a single session.
Step 1: Get session detail
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts session-detail <session-id>This returns: session summary, token usage (input/output/cache), models used, tools called, and associated task lists with their tasks.
Step 2: Present summary
Show a formatted summary:
- Session: ID, project, date, duration
- Tokens: input, output, cache read, cache create
- Models: which models were used and how many turns each
- Tools: top tools used with counts
- Tasks: associated task lists and task status summary
Note on resumed sessions
If is_resumed is true in the stats, this session was started via claude --resume or claude --continue. The JSONL only contains messages from the resumed portion — earlier context from the parent session is not included. Mention this to the user so they understand why the transcript may appear to start mid-conversation.
Step 3: Show messages (optional)
If the user wants to see the conversation:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-parser.ts messages <session-path> --limit 20For more messages, increase --offset and --limit:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-parser.ts messages <session-path> --offset 20 --limit 20To include tool call details:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-parser.ts messages <session-path> --include-tools --limit 20Does 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
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.