Borrowing it
Nothing to install: this file belongs to design-and-deliver/claude-code-autoconfig. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/design-and-deliver/claude-code-autoconfig/main/.claude/commands/analyze-session.mdgit clone --depth 1 https://github.com/design-and-deliver/claude-code-autoconfigWrote 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.
[](https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/analyze-session)<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/analyze-session"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/analyze-session.svg" alt="Measured on agentmods" height="20"></a>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.00013 | $0.00958 |
| Opus 5 | $0.00006 | $0.00479 |
| Sonnet 5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00001 | $0.00096 |
Grade A, and why
analyze-session 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Session
Explain where a session's tokens went and what to change next time. The heavy lifting is
deterministic (the --analyze digest — pure node, no LLM, ~free) and has ALREADY RUN: the
injected output below was generated at prompt time, before the model saw this prompt. The
model interprets ONLY the digest.
Argument: $ARGUMENTS — a session-id prefix, the exact project/sid8 label shown on
/usage-report's LAST 5 HOURS rows (both forms resolve), or a full transcript path.
Digest (injected at prompt time — zero model round trips)
!node .claude/hooks/token-guard.js --analyze $ARGUMENTS
Step 1: check the injected digest
The digest above already ran — re-running it via Bash wastes the round trip the injection exists to save. Route on its first line:
- Starts with
SESSION→ healthy; go straight to Step 2. - Says
usage:→ the command was invoked with no argument: derive the CURRENT session's transcript path (~/.claude/projects/<project-slug>/<session-id>.jsonl, same derivation as/usage-report) and runnode .claude/hooks/token-guard.js --analyze <path>via Bash — the only case that needs a model-driven run. - Says
ambiguous→ show the candidate list and ask which one was meant. - Says
no transcript matches→ report that verbatim and point at/usage-report's row labels as the source of valid sids.
Step 2: interpret — the digest ONLY
Hard rule: never read the raw transcript. Analyzing a 40M-token session must not itself load 40M tokens — if the digest can't answer something, say what's missing instead of digging. (Targeted transcript digging is future work, behind an explicit user approval.)
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.
- 6d ago First seen · 72 lines · 13 tokens per session scan A 60eaa2c963c8
analyze-session is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 958 once invoked, about $0.0001 per session on Opus 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.