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.
git clone --depth 1 https://github.com/KevinZai/commanderWrote 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.
[](https://agentmods.dev/commands/kevinzai/commander/ccc-checkpoint)<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.
<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>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.00039 | $0.01023 |
| Opus 5.5 | $0.00016 | $0.00409 |
| Sonnet 5.5 | $0.00008 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00102 |
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. 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.
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
-
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 asbuild=FAIL. -
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") - 🟢 Commit — stage the tracked changes and commit as
-
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 -
Verify with
tail -1 .claude/checkpoints.logandgit cat-file -t $SHA(expectscommit), then report the name and SHA.
Verify
-
Read the line for
<name>from the log. If it is missing, list the available names and stop. -
Compare the current state with the checkpoint SHA.
git diff --name-status <sha> # A = added, M = modified, D = deleted git diff --stat <sha> -
Run
/ccc-verifyfor the current build, test and coverage results. -
Report:
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.
- 5d ago Changed · +23 lines · +20 tokens per session scan A → B d951cd2f31f5
- 1mo ago First seen · 79 lines · 19 tokens per session scan A 91f86d7216dd
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.
Other commands, from other repositories
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
commit
Split the changes into atomic commits, preflight and push them. Pass --skip-preflight or --no-push to skip a step.
autocommit
Toggle auto git commits on/off for this project. Run without args to see status, or with "on"/"off" to set.
commit-message
Generate a conventional commit message from staged changes.