session-wrap

A command that closes a coding session only after a safety check and writes a handoff for the next session. The handoff can include updates, ledger entries, and a NEXTSESSION.md file.

In plain words
What is it for?
Use it when ending work in a project, especially when another session or developer will continue from the current state.
Why use it?
It helps prevent stopping with unrecorded work or unclear next steps. Options allow you to force the stop or control whether changes are committed.

Command

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/akshayrao14/git-practices/session-wrap
Clone the repo
git clone --depth 1 https://github.com/akshayrao14/git-practices
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 161 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.00033 $0.00161
Opus 5 $0.00016 $0.00081
Sonnet 5 $0.00007 $0.00032
Haiku 4.5 $0.00003 $0.00016

Measured 2d ago against content hash 222e804ea0b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

session-wrap 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.

skills/session-loop/commands/session-wrap.md · 14 lines

What it actually says

Invoke the session-loop skill with focus=wrap. Load sub/wrap.md from the skill directory and follow it exactly.

Args (optional):

  • --force <reason> — override the stop-safety gate. Reason is logged into the handoff.
  • --auto-commit — skip the commit prompt and commit handoff artifacts immediately.
  • --no-commit — skip the commit prompt and do not commit (for non-interactive runs).

Acts on the current working directory's project. Reads/writes NEXT_SESSION.md, UPDATES.md, and the discovered ledger.

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. 2d ago First seen · 14 lines · 33 tokens per session scan A 222e804ea0b0

Subscribe to this mod's changes

session-wrap is a command published in the GitHub repository akshayrao14/git-practices (0 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 161 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-31.