A command that updates a session summary file with the current project status, findings, progress, and important documents. The file is used to restore context after a conversation reset.

It helps record the session goal, current focus, repository state, changes, commits, stashes, and newly relevant documents.

It prevents important work details from being lost when a coding session is interrupted or continued later.

checkpoint — Command for coding agents by mgonzalezbaile: A command that updates a session summary file with…

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/mgonzalezbaile/claudex/checkpoint

Clone the repo

git clone --depth 1 https://github.com/mgonzalezbaile/claudex

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 913 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00913
Opus 5	$0.00000	$0.00456
Sonnet 5	$0.00000	$0.00183
Haiku 4.5	$0.00000	$0.00091

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

Security

Grade A, and why

checkpoint 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 3d 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.

src/profiles/commands/checkpoint.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Checkpoint Command

Update the current session overview file with all findings, progress, and current status. This command helps maintain context across conversation resets and allows you to resume work seamlessly.

Step 1: Gather Current State

Run these commands to understand the current project state:

# Check git status
git status --short

# Show current branch
git branch --show-current

# Show uncommitted changes
git diff --stat

# Check for stashed changes
git stash list

# Show recent commits
git log --oneline -5

Step 2: Identify Session File Location

The session overview file is located at:

.claudex/sessions/{session-id}/session-overview.md

Determine the current session ID from the session context provided at conversation start.

Step 3: Update Session Overview

Update the session overview file with the following sections:

Session Summary

Keep the original goal/purpose of the session
Add any clarifications or scope changes that occurred

Current Focus

Update with what you're currently working on
If task is complete, describe what was just finished
If blocked, describe the blocker clearly

Key Documents

Add any new documentation files created
Add any modified configuration files
Include execution plans, architecture docs, test reports
Use absolute paths for all file references

Progress Timeline

Add a new timestamped entry describing:
- What was accomplished
- What decisions were made
- What files were modified/created
- Any blockers encountered
- Next planned steps
Format: - **YYYY-MM-DDTHH:MM:SSZ** - Description of progress

Status Field

Update the status to one of:

In Progress - Active work ongoing
Blocked - Waiting on external input or resolution
Completed - All tasks finished
Paused - Work temporarily suspended

Last Updated Timestamp

Update the footer timestamp
Include a brief description of the update type
Format: *Last updated: YYYY-MM-DDTHH:MM:SSZ (Checkpoint: brief description)*

Read the full file on GitHub · 154 lines

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.

3d ago First seen · 154 lines · 0 tokens per session scan A 12150f28423f

Subscribe to this mod's changes

checkpoint is a command published in the GitHub repository mgonzalezbaile/claudex (23 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 913 tokens. 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.

Memory and context

checkpoint