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.
npx agentmods add commands/damusix/atomic-claude/session-reportgit clone --depth 1 https://github.com/damusix/atomic-claudeWhat 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 | $0.00031 | $0.00963 |
| Opus 5 | $0.00015 | $0.00481 |
| Sonnet 5 | $0.00006 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
session-report 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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Long-running branch spanning multiple Claude Code sessions. The eventual commit (or squash) needs the why behind the work, but git diff alone loses that. Run /session-report at the end of a session to capture intent for the future commit-message synthesis.
Opt-in only. Does not auto-fire.
Refuse to run if
- Working tree clean AND no unstaged changes since last commit →
refused: no changes since last commit — nothing to report.
Steps
-
Determine branch scope key:
git branch --show-current. If empty (detached HEAD), usegit rev-parse --short HEADand warn the user:detached HEAD — report scoped to <sha> not a branch.
-
Compute paths:
- Dir:
atomic where --json'sreportsfield — already branch-scoped, with the legacy fallback folded in. Never construct it by hand. - Filename:
<YYYY-MM-DD-HHMM>-<slug>.md. Slug from$ARGUMENTSif provided; otherwise infer from the most prominent change in the working tree (one or two kebab-case words). - On filename collision (same minute + same slug): append
-2,-3, etc.
- Dir:
-
Gather signal:
git status --porcelain— list of touched files (staged + unstaged).git diff --statandgit diff --cached --stat— magnitude per file.- Recent conversation context — what was tried, what was rejected, what the user clarified mid-flight.
-
Write the report: seed the computed path from the embedded template —
atomic template session-report > <path>— then fill every<angle-bracket>placeholder (frontmatter +## What changed+## Why+ optional## Open threads) and delete the guidance comment. Ifatomicis absent or the verb errors, stop:document template unavailable (atomic template session-report failed) — install/update the atomic binary. cannot proceed. -
Report path to the user:
wrote <reports-dir>/<file>.md, using thereportspath fromatomic where --json.
<output_format>
Voice
atomic-writing voice at the length budget it gives a short-lived state file: bullets and short paragraphs, no narrative. Not atomic output style, which governs Claude's replies rather than file contents. Internal context that the commit-message synthesis will read.
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.
- 2d ago First seen · 65 lines · 31 tokens per session scan A 48d80237a797
session-report is a command published in the GitHub repository damusix/atomic-claude (83 stars, last pushed 8d ago), licensed MIT. It adds 31 tokens to every session and 963 once invoked, about $0.0002 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-30.
Other commands, from other repositories
commit
Auto-stage, review, and commit all changes with a conventional commit message.
ship
Commit all changes and push to remote in one operation (combines /commit and /push).
close
End session with verification, commits, and documentation.
commit-all
Group all changes semantically and commit each group separately.
version
Display current guide and Claude Code versions.
go-review
Go code review for idiomatic patterns.