wrap-up

An end-of-session checklist that verifies code and records a structured handoff in project notes.

In plain words
What is it for?
Use it after a work session to run configured checks, rewrite the session primer, record important decisions, list risks and next steps, and identify key files.
Why use it?
It leaves the next coding session with a clear record of what changed, what works, what remains, and what should happen next.

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/codeverbojan/claude-code-kickstart/wrap-up
Clone the repo
git clone --depth 1 https://github.com/codeverbojan/claude-code-kickstart

Made for: Claude Code.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 542 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00013 $0.00542
Opus 5 $0.00006 $0.00271
Sonnet 5 $0.00003 $0.00108
Haiku 4.5 $0.00001 $0.00054

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

Security

Grade B, and why

wrap-up scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- `signals_captured`: `grep -c "$(date -u +%Y-%m-%d)" .claude/signals.jsonl 2>/dev/null || echo 0`
.claude/commands/wrap-up.md · 86 lines

What it actually says

Session Wrap-Up

1. Verify

Run typecheck/lint/tests if any code changed. Note pass/fail. Skip if nothing was touched.

2. Rewrite primer.md

Overwrite primer.md with exactly this structure (replace bracketed hints):

# Session Primer

## Last Session
[date]: [1–2 sentence summary]

## What Changed
- [file]: [why]

## Current State
[what works, what doesn't, what's partial]

## Uncommitted Changes
[list, or "None"]

## Test Status
- Type-check: PASS | FAIL | NOT CONFIGURED
- Lint: PASS | FAIL | NOT CONFIGURED
- Tests: PASS | FAIL | NOT CONFIGURED (X passed, Y failed)

## Decisions Made
[bullets, or "None"]

## Risks
[fragile or incomplete bits]

## Next Steps
1. [actionable]
2. [actionable]

## Next Recommended Command
[exact slash command, e.g. `/onboard deep finish auth`]

## Key Files
- [files next session should read first]

3. Append to decisions.md (only if real decisions were made)

Append new entries — never overwrite. Skip trivial choices (naming, formatting). Log choices that would be re-litigated without context: tech picks, architecture, pattern decisions, scope cuts. Skip if a matching title already exists.

Format:

## [date]: [title]
**Choice:** …
**Why:** …
**Context:** …

4. Append to gotchas.md (only if mistakes happened)

Numbered rule per mistake. Skip if none.

5. Append metrics line

echo '{"date":"YYYY-MM-DD","files_touched":N,"verification_runs":N,"gotchas_added":N,"signals_captured":N,"decisions_logged":N}' >> .claude/metrics.jsonl

Counts (deterministic — don't guess from memory):

  • files_touched: git diff --name-only | wc -l
  • signals_captured: grep -c "$(date -u +%Y-%m-%d)" .claude/signals.jsonl 2>/dev/null || echo 0
  • Others: count what you actually added this session.

6. Report

One paragraph: what shipped, uncommitted changes, failing checks. No epic summary — the user will read primer.md.

$ARGUMENTS

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 · 86 lines · 13 tokens per session scan B 00a2544a0870

Subscribe to this mod's changes

wrap-up is a command published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 542 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.