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/NovasPlace/CSMWrote 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/novasplace/csm/csm-checkpoint)<a href="https://agentmods.dev/commands/novasplace/csm/csm-checkpoint"><img src="https://agentmods.dev/badge/commands/novasplace/csm/csm-checkpoint.svg" alt="Measured on agentmods" 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.00012 | $0.00155 |
| Opus 5 | $0.00006 | $0.00077 |
| Sonnet 5 | $0.00002 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
csm-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 8d 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.
What it actually says
Manage CSM checkpoints: $ARGUMENTS
- Resolve
projectRootto the current workspace root. - If the argument is "list" (or empty), call
list_checkpointsand summarize recent checkpoints. - Otherwise call
create_checkpointcapturing the current state with the given label — only when that state would be expensive to reconstruct. - Use
expand_checkpoint_refto inspect a specific checkpoint the user names.
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.
- 8d ago First seen · 13 lines · 12 tokens per session scan A 60ec168350a7
csm-checkpoint is a command published in the GitHub repository NovasPlace/CSM (42 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 155 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-08-30.
Other commands, from other repositories
sessions
Manage Gemini Code session history, aliases, and session metadata.
compress
Save this Claude Code session to the vault and update the semantic memory index.
checkpoint
Save a mid-session checkpoint — for continuity between sessions of the same day.
resume
Load context from the vault before starting work.
preserve
Scan this conversation and silently save anything worth permanent memory.
memory-evolve
Phase 3.4 self-evolving memory. Convert reuse + routing-miss signals into PR-ready proposals (skill drafts + routing-rule additions). Never auto-applies.