session

A command for saving the current coding conversation and its project state to a Git repository. It records the session, journal, focus, and context files, then commits and pushes the updates.

In plain words
What is it for?
Use it at the end of a work session to create a dated session note, update project state, commit the changes, and push them to GitHub.
Why use it?
It preserves what happened and what matters next, so work can be resumed or reviewed later.

Command for Claude Code

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.

agentmods
npx agentmods add commands/teejayen/arc/session
Clone the repo
git clone --depth 1 https://github.com/teejayen/arc

Made for: Claude Code.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 124 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00009 $0.00124
Opus 5 $0.00005 $0.00062
Sonnet 5 $0.00002 $0.00025
Haiku 4.5 $0.00001 $0.00012

Measured yesterday against content hash 310ee855a7ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

.claude/commands/session.md · 16 lines

What it actually says

Save this conversation and update state files.

Use the session-save skill (.claude/skills/session-save/SKILL.md) to:

  1. Create session file in sessions/YYYY-MM-DD-HHMM-topic.md
  2. Append to state/journal.jsonl
  3. Update state/focus.md if priorities shifted
  4. Update state/session-context.json
  5. Git commit and push
  6. Show random quote from quotes.md (if it exists)
  7. Offer to extract any decisions
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.

  1. yesterday First seen · 16 lines · 9 tokens per session scan A 310ee855a7ba

Subscribe to this mod's changes

session is a command published in the GitHub repository teejayen/arc (5 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 124 once invoked, about $0.0000 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.