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/hgahlot/claude-flow/checkpointgit clone --depth 1 https://github.com/hgahlot/claude-flowWrote 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/hgahlot/claude-flow/checkpoint)<a href="https://agentmods.dev/commands/hgahlot/claude-flow/checkpoint"><img src="https://agentmods.dev/badge/commands/hgahlot/claude-flow/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.00312 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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 5d 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 — Save Current State to STATE.md
Capture a snapshot of the current session state for continuity across sessions.
Instructions
- Identify completed work — list tasks finished since last checkpoint
- Identify current position — what task is in progress right now
- Identify next tasks — what comes next in the plan
- Note any blockers — unresolved issues, open questions, external dependencies
- Write to STATE.md — overwrite with updated content
STATE.md Format
# Session State
## Last Session
Ended: <ISO timestamp>
## Last Completed Task
<Task ID and description from the plan>
Evidence: <brief description of verification performed>
## Current Task (In Progress)
<Task ID and description, or "none">
## Next Tasks Queue
1. <Task ID>: <description>
2. <Task ID>: <description>
3. <Task ID>: <description>
## Blockers
- <blocker description> — waiting on: <what/who>
## Recent Decisions
- <decision made and why — only non-obvious decisions>
## Activity Log
- [timestamp] <significant action taken>
Rules
- Keep STATE.md under 200 lines
- When it approaches 200 lines, summarize completed milestones into ROADMAP.md
- Always include evidence for the last completed task
- Blockers must name what is blocking, not just "blocked"
- After writing STATE.md, confirm: "Checkpoint saved."
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.
- 5d ago First seen · 49 lines · 0 tokens per session scan A d76b5f23887d
checkpoint is a command published in the GitHub repository hgahlot/claude-flow (53 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 312 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.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.