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/jonathanprozzi/claude-utilsWrote 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/jonathanprozzi/claude-utils/checkpoint)<a href="https://agentmods.dev/commands/jonathanprozzi/claude-utils/checkpoint"><img src="https://agentmods.dev/badge/commands/jonathanprozzi/claude-utils/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/jonathanprozzi/claude-utils/checkpoint"><img src="https://agentmods.dev/badge/commands/jonathanprozzi/claude-utils/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.00000 | $0.01402 |
| Opus 5.5 | $0.00000 | $0.00561 |
| Sonnet 5.5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a timestamped checkpoint in the current daily session transcript.
Command Usage
/checkpoint- Create checkpoint with auto-generated summary/checkpoint [note]- Create checkpoint with specific note/context
What This Command Does
-
Identify the current transcript file:
- Look for
ai-chats/transcripts/YYYY-MM-DD/daily-session-YYYY-MM-DD.mdin the current vault - Use today's date
- Look for
-
Archive the current conversation:
- Create archive directory:
ai-chats/transcripts/YYYY-MM-DD/archives/ - Export full transcript to Markdown:
session-YYYY-MM-DD-HHMM-full.md - This preserves the full conversation at checkpoint time
- Create archive directory:
-
Generate checkpoint entry:
- Current timestamp (e.g.,
### ~3:45pm - Checkpoint) - Link to the archived full transcript
- If user provided a note, use that as the summary line
- Otherwise, generate a brief summary of what's been accomplished
- Include structured data matching PreCompact format
- Current timestamp (e.g.,
-
Append to transcript:
- Add the checkpoint entry to the "Session Log" section (before "## Session Handoff")
- Include key activities with [[wiki-links]]
- Include summary points
-
Update daily note:
- Find today's daily note at
journals/YYYY-MM-DD.md - Increment the checkpoint count (e.g.,
*(2 checkpoints)*→*(3 checkpoints)*) - Add a nested bullet with deep link to the checkpoint section
- Find today's daily note at
Checkpoint Entry Format (Transcript)
### ~[TIME] - Checkpoint
[Summary line - user note or auto-generated]. [[ai-chats/transcripts/YYYY-MM-DD/archives/session-YYYY-MM-DD-HHMM-full|Full transcript]]
**Session:** [[Session Type]] | [N] messages | [N] tool calls | [N] created | [N] modified
**Key Activities:**
- Created: `path/to/file` ([[Language]])
- Modified: `path/to/file` ([[Language]])
- [Other notable activities with wiki-links]
**Summary:**
- Key accomplishment 1 with [[wiki-links]]
- Key accomplishment 2
- Decisions or insights
---
Daily Note Entry Format
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 · 149 lines · 0 tokens per session scan A 88c9fdc7a95c
checkpoint is a command published in the GitHub repository jonathanprozzi/claude-utils (11 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,402 tokens. 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.
checkpoint compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| checkpointjonathanprozzi/claude-utils | Command | 11 | 8mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |