ccc-checkpoint

ccc-checkpoint is a command for coding agents from KevinZai/commander. It costs 19 tokens per session (421 once invoked), scanned A, original, MIT.

Create or verify a workflow checkpoint — git commit, state snapshot, and safety gate before proceeding.

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/kevinzai/commander/ccc-checkpoint
Clone the repo
git clone --depth 1 https://github.com/KevinZai/commander

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.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.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 421 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00019 $0.00421
Opus 5 $0.00010 $0.00211
Sonnet 5 $0.00004 $0.00084
Haiku 4.5 $0.00002 $0.00042

Measured today against content hash 91f86d7216dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ccc-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 today.

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/ccc-checkpoint.md · 79 lines

What it actually says

Checkpoint Command

Create or verify a checkpoint in your workflow.

Usage

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

Create Checkpoint

When creating a checkpoint:

  1. Run /verify quick to ensure current state is clean
  2. Create a git stash or commit with checkpoint name
  3. Log checkpoint to .claude/checkpoints.log:
echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .claude/checkpoints.log
  1. Report checkpoint created

Verify Checkpoint

When verifying against a checkpoint:

  1. Read checkpoint from log

  2. Compare current state to checkpoint:

    • Files added since checkpoint
    • Files modified since checkpoint
    • Test pass rate now vs then
    • Coverage now vs then
  3. Report:

CHECKPOINT COMPARISON: $NAME
============================
Files changed: X
Tests: +Y passed / -Z failed
Coverage: +X% / -Y%
Build: [PASS/FAIL]

List Checkpoints

Show all checkpoints with:

  • Name
  • Timestamp
  • Git SHA
  • Status (current, behind, ahead)

Workflow

Typical checkpoint flow:

[Start] --> /checkpoint create "feature-start"
   |
[Implement] --> /checkpoint create "core-done"
   |
[Test] --> /checkpoint verify "core-done"
   |
[Refactor] --> /checkpoint create "refactor-done"
   |
[PR] --> /checkpoint verify "feature-start"

Arguments

$ARGUMENTS:

  • create <name> - Create named checkpoint
  • verify <name> - Verify against named checkpoint
  • list - Show all checkpoints
  • clear - Remove old checkpoints (keeps last 5)
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. today 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 yesterday), licensed MIT. It adds 19 tokens to every session and 421 once invoked, about $0.0001 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-09-03.