A command for recording important milestones in Git, the version-control system used to track code changes. It stores a name, date, and commit reference in a project log.

Use it to create, verify, or list named project checkpoints with commands such as `/checkpoint create`, `/checkpoint verify`, and `/checkpoint list`.

It makes it easier to see what changed since a milestone and check the current test status later. It is meant for work spanning multiple days, not quick in-session undo.

checkpoint — Command for Claude Code by cloudnative-co

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.

Clone the repo

git clone --depth 1 https://github.com/cloudnative-co/claude-code-starter-kit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/cloudnative-co/claude-code-starter-kit/checkpoint/github.svg)](https://agentmods.dev/commands/cloudnative-co/claude-code-starter-kit/checkpoint)

Your own site

<a href="https://agentmods.dev/commands/cloudnative-co/claude-code-starter-kit/checkpoint"><img src="https://agentmods.dev/badge/commands/cloudnative-co/claude-code-starter-kit/checkpoint/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/cloudnative-co/claude-code-starter-kit/checkpoint"><img src="https://agentmods.dev/badge/commands/cloudnative-co/claude-code-starter-kit/checkpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 356 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00000	$0.00356
Opus 5.5	$0.00000	$0.00142
Sonnet 5.5	$0.00000	$0.00071
Haiku 4.5	$0.00000	$0.00036

Measured 1mo ago against content hash 14a790bc9fbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

commands/checkpoint.md · 46 lines

What it actually says

Checkpoint Command

Record cross-session git milestones. In-session rollback is handled by Claude Code's native checkpoint/rewind (Esc Esc / /rewind) — use this command only for multi-day milestones you want recorded in git.

Native rewind only restores files changed through Claude's file editing tools (Edit, Write, NotebookEdit). Changes made with Bash (sed -i, heredocs, mv, cp) are not tracked; rely on git for those.

Usage

/checkpoint [create|verify|list] [name]

Create Checkpoint

Run /verify quick to ensure current state is clean
Create a git commit or tag with the checkpoint name
Log the checkpoint to .claude/checkpoints.log:

echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .claude/checkpoints.log

Report checkpoint created

Verify Checkpoint

Read the checkpoint SHA from the log
Show what changed since then: git diff --stat <sha>..HEAD
Run the test suite once and report the current status (the log records only date/name/SHA — there is no historical test/coverage data to compare against)

List Checkpoints

Show all checkpoints with name, timestamp, git SHA, and whether HEAD is at, ahead of, or behind each.

Arguments

$ARGUMENTS:

create <name> - Record a milestone
verify <name> - Diff + current test status against a milestone
list - Show recorded milestones

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.

1mo ago Changed · +4 lines 14a790bc9fbf
1mo ago First seen · 42 lines · 0 tokens per session scan A ad75ce27aef3

Subscribe to this mod's changes

checkpoint is a command published in the GitHub repository cloudnative-co/claude-code-starter-kit (153 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 356 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.

Commits Git and workflow

checkpoint