Borrowing it
Nothing to install: this file belongs to znlnzi/claude-config-studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/znlnzi/claude-config-studio/main/.claude/commands/checkpoint.mdgit clone --depth 1 https://github.com/znlnzi/claude-config-studioWrote 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/znlnzi/claude-config-studio/checkpoint)<a href="https://agentmods.dev/commands/znlnzi/claude-config-studio/checkpoint"><img src="https://agentmods.dev/badge/commands/znlnzi/claude-config-studio/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/znlnzi/claude-config-studio/checkpoint"><img src="https://agentmods.dev/badge/commands/znlnzi/claude-config-studio/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.00012 | $0.00219 |
| Opus 5.5 | $0.00005 | $0.00088 |
| Sonnet 5.5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
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 2mo 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
/checkpoint - 检查点管理
创建工作快照，跟踪开发进度。
子命令
/checkpoint create [name]
创建一个命名检查点，记录当前状态：
- 文件变更列表
- 测试通过率
- 代码覆盖率
- 构建状态
/checkpoint verify [name]
将当前状态与指定检查点比较：
- 新增/修改的文件
- 测试结果变化
- 覆盖率变化
- 构建状态变化
/checkpoint list
显示所有已保存的检查点。
使用场景
典型开发周期：
- 开始工作前创建检查点
- 每个里程碑创建检查点
- 提交 PR 前对比检查点
- 回顾变更确保质量
检查点文件格式
检查点保存在 .claude/checkpoints/ 目录下。
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.
- 2mo ago First seen · 40 lines · 12 tokens per session scan A 93a844be36fa
checkpoint is a command published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 8mo ago), licensed MIT. It adds 12 tokens to every session and 219 once invoked, about $0.0000 per session on Opus 5.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-31.
Other commands, from other repositories
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
vs-queue
Show what is waiting on the operator, then the live / in-flight board tasks.
anchors
List what each requirement tag anchors to (read-only).
task-management
Query and update recorded planning and research portfolio state across tasks, topics, papers, outputs, submissions, venues, people, institutions, and deadlines. Use when asking what is already recorded, including institution- or venue-associated topics, or when doing daily planning and weekly review. For venue…
project-deck
Create a concise presentation deck that communicates a project's current state, decisions, evidence, risks, and next steps. Use when preparing a project update for collaborators, supervisors, or stakeholders. Not for a research talk centered on one paper; use $talk-deck.
next
Suggest the most likely next workflow action based on current context.