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.
npx agentmods add commands/llcoolblaze/claude-boris/checkpointgit clone --depth 1 https://github.com/llcoolblaze/claude-borisWrote 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/llcoolblaze/claude-boris/checkpoint)<a href="https://agentmods.dev/commands/llcoolblaze/claude-boris/checkpoint"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/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 | $0.00016 | $0.00582 |
| Opus 5 | $0.00008 | $0.00291 |
| Sonnet 5 | $0.00003 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
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 4d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Checkpoint
Current State
!git status --short 2>/dev/null || echo "Not a git repo"
!git stash list 2>/dev/null | grep "checkpoint:" | head -5
!git tag -l "checkpoint/*" 2>/dev/null | tail -5
Checkpoint Protocol
Checkpoint Name
Name: $ARGUMENTS
If no name provided, generate: checkpoint-$(date +%Y%m%d-%H%M%S)
1. Save Current State
Stage all changes:
git add -A
Create stash checkpoint:
git stash push -m "checkpoint:$NAME"
Create tag checkpoint (persistent):
git tag -a "checkpoint/$NAME" -m "Checkpoint: $NAME - $(date)"
2. Checkpoint Types
| Type | Storage | Persistence | Use Case |
|---|---|---|---|
| Stash | Local stash | Until dropped | Quick saves |
| Tag | Git tags | Until deleted | Important milestones |
| Branch | Git branch | Permanent | Major features |
3. Execute
For quick checkpoint (stash):
git add -A
git stash push -m "checkpoint:$NAME"
echo "📍 Checkpoint created: $NAME"
For persistent checkpoint (tag):
git add -A
git commit -m "checkpoint: $NAME" --allow-empty
git tag "checkpoint/$NAME"
echo "📍 Persistent checkpoint: $NAME"
4. Report
📍 Checkpoint Created
Name: [checkpoint name]
Type: [stash/tag]
Time: [timestamp]
Files included: [count]
Restore with: /rollback [name]
List checkpoints: /checkpoints
5. Record in Memory Bank
Update .claude/memory/activeContext.md:
## Checkpoints
- [name] created at [time] - [reason]
Usage Examples
Create named checkpoint:
/checkpoint before-refactor
Create auto-named checkpoint:
/checkpoint
With description:
/checkpoint pre-auth-changes
Checkpoint Best Practices
- Before major refactors - Always checkpoint first
- After working code - Save good states
- Before risky changes - Insurance policy
- End of session - Preserve work state
- Clear names -
pre-authnotcp1
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.
- 4d ago First seen · 113 lines · 16 tokens per session scan A c38ced4f7077
checkpoint is a command published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 582 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.