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/kumaran-is/claude-code-onboarding/checkpointgit clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/checkpoint)<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/checkpoint"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/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.00000 | $0.00656 |
| Opus 5 | $0.00000 | $0.00328 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00066 |
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 today.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/checkpoint — Named Checkpoints for Long Sessions
Save named snapshots of session state so you can compare before/after or roll back context.
Modes
/checkpoint create <name>
Save a checkpoint at the current point in the session.
Actions:
- Run
git diff --stat HEAD— capture list of changed files - Run
git rev-parse HEAD— capture current SHA - Append to
.claude/checkpoints.log:{ISO-8601-timestamp}|{name}|{git-SHA}|{changed-file-count} files changed - Report:
✅ Checkpoint saved: {name} SHA: {git-SHA} Changed files: {list from git diff --stat}
/checkpoint verify <name>
Compare current state against a saved checkpoint.
Actions:
- Read
.claude/checkpoints.log— find entry matching{name} - Run
git diff {saved-SHA} HEAD --stat - Report:
Checkpoint: {name} (saved at {timestamp}) Base SHA: {saved-SHA} Current SHA: {current-SHA} Files changed since checkpoint: {git diff output} Delta: +{added} -{removed} lines across {N} files
/checkpoint list
Show all saved checkpoints for this session.
Actions:
- Read
.claude/checkpoints.log - Report table:
| Name | Saved At | SHA | Files | |------|----------|-----|-------| | {name} | {timestamp} | {short-SHA} | {count} | - If file is empty or missing: "No checkpoints saved yet. Use
/checkpoint create <name>to save one."
/checkpoint clear
Remove all entries from .claude/checkpoints.log.
Actions:
- Confirm: "This will delete all {N} checkpoints. Proceed? (yes/no)"
- On yes: overwrite
.claude/checkpoints.logwith empty content - Report: "✅ Checkpoints cleared."
Log Format
File: .claude/checkpoints.log
One entry per line, pipe-separated:
2026-03-29T14:22:00Z|pre-refactor|abc1234def|7 files changed
2026-03-29T15:45:00Z|post-auth|def5678abc|3 files changed
When to Use
- Before a large refactor:
/checkpoint create pre-refactor - After completing a phase:
/checkpoint create phase-1-complete - Before trying a risky approach:
/checkpoint create before-experiment - To verify progress:
/checkpoint verify pre-refactor
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.
- today First seen · 85 lines · 0 tokens per session scan A ab517f07d652
checkpoint is a command published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 656 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-09-03.
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.