ccc-checkpoint

ccc-checkpoint is a command for Claude Code from KevinZai/commander. It costs 39 tokens per session (1,023 once invoked), scanned B, a copy of checkpoint, MIT.

A workflow checkpoint that records a named point in a Git project and can compare the current state with it. Git is a system for tracking file changes and commits.

In plain words
What is it for?
Use it to create, verify, or list checkpoints, including file changes, test results, coverage, and build status.
Why use it?
It provides a known state to return to or compare against before continuing with risky or multi-step work.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: names the AskUserQuestion tool.

Good fit Use it to create, verify, or list checkpoints, including file changes, test results, coverage, and build status.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/kevinzai/commander/ccc-checkpoint
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/KevinZai/commander

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.

agentmods badge for ccc-checkpoint

README.md
[![agentmods](https://agentmods.dev/badge/commands/kevinzai/commander/ccc-checkpoint/github.svg)](https://agentmods.dev/commands/kevinzai/commander/ccc-checkpoint)
Your own site
<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-checkpoint"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-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.

agentmods 80×15 button for ccc-checkpoint

Your own site · 80×15
<a href="https://agentmods.dev/commands/kevinzai/commander/ccc-checkpoint"><img src="https://agentmods.dev/badge/commands/kevinzai/commander/ccc-checkpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,023 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod 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.1 $0.00039 $0.01023
Opus 5.5 $0.00016 $0.00409
Sonnet 5.5 $0.00008 $0.00205
Haiku 4.5 $0.00004 $0.00102

Measured 5d ago against content hash d951cd2f31f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

ccc-checkpoint 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 5d 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.

4. Verify with `tail -1 .claude/checkpoints.log` and `git cat-file -t $SHA` (expects `commit`), then report the name and SHA.
Origin

This is a copy

91% identical to checkpoint — 133 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/ccc-checkpoint.md · 102 lines

How it starts

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

/ccc-checkpoint — named workflow checkpoints

CC Commander · /ccc-checkpoint · snapshot a known-good state, then measure drift against it.

Arguments

$ARGUMENTS: create <name> · verify <name> · list · clear (keeps the last 5).

The log is .claude/checkpoints.log, one line per checkpoint:

<YYYY-MM-DD-HH:MM> | <name> | <sha> | build=<PASS|FAIL> tests=<passed>/<failed|-> coverage=<pct|->

Create

  1. Run /ccc-verify quick (build and types). If it fails, report the errors and ask (AskUserQuestion, plain-text question where unavailable): 🟢 Stop and fix first · Create the checkpoint anyway, recorded as build=FAIL.

  2. Ask how to snapshot:

    • 🟢 Commit — stage the tracked changes and commit as chore: checkpoint <name>.
    • Snapshot without committing — record a stash object that leaves the working tree untouched.
    # Commit
    git add -u && git commit -m "chore: checkpoint <name>"
    SHA=$(git rev-parse --short HEAD)
    
    # Snapshot without committing (falls back to HEAD when the tree is clean)
    SHA=$(git stash create "checkpoint <name>"); SHA=${SHA:-$(git rev-parse HEAD)}
    git stash store -m "checkpoint <name>" "$SHA" 2>/dev/null; SHA=$(git rev-parse --short "$SHA")
    
  3. Append the log line, filling tests and coverage only if a test run happened in this step (otherwise -).

    mkdir -p .claude && echo "$(date +%Y-%m-%d-%H:%M) | <name> | $SHA | build=<PASS|FAIL> tests=- coverage=-" >> .claude/checkpoints.log
    
  4. Verify with tail -1 .claude/checkpoints.log and git cat-file -t $SHA (expects commit), then report the name and SHA.

Verify

  1. Read the line for <name> from the log. If it is missing, list the available names and stop.

  2. Compare the current state with the checkpoint SHA.

    git diff --name-status <sha>      # A = added, M = modified, D = deleted
    git diff --stat <sha>
    
  3. Run /ccc-verify for the current build, test and coverage results.

  4. Report:

Read the full file on GitHub · 102 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.

  1. 5d ago Changed · +23 lines · +20 tokens per session scan A → B d951cd2f31f5
  2. 1mo ago First seen · 79 lines · 19 tokens per session scan A 91f86d7216dd

Subscribe to this mod's changes

ccc-checkpoint is a command published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,023 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 91% identical to checkpoint, differing in 133 lines, and is treated as a copy.