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/kristijankopacevic/optiflow-mcpWrote 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/kristijankopacevic/optiflow-mcp/checkpoint)<a href="https://agentmods.dev/commands/kristijankopacevic/optiflow-mcp/checkpoint"><img src="https://agentmods.dev/badge/commands/kristijankopacevic/optiflow-mcp/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/kristijankopacevic/optiflow-mcp/checkpoint"><img src="https://agentmods.dev/badge/commands/kristijankopacevic/optiflow-mcp/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.00038 | $0.00356 |
| Opus 5 | $0.00019 | $0.00178 |
| Sonnet 5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
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 8d 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
Save an optiflow session-handoff checkpoint and tell the user where it was written.
The real command Claude Code exposes for this is /optiflow:checkpoint (the
plugin namespace prefix is not optional — there is no bare
/checkpoint). It writes a JSON file under .optiflow/checkpoints/ in the
current project, containing:
- the current git branch/HEAD (auto-derived via real
gitcalls;nullifcwdisn't a repo or has no commits yet), - the current working directory,
$ARGUMENTS(if any) as the checkpoint's soledecisions[]entry — this is the ONLY waydecisions[]/nextSteps[]/openFiles[]get populated; a hook-triggered auto-checkpoint (onPreCompact/SessionEnd) can never supply free-text like this, so if the user wants a next-session-ready summary,$ARGUMENTSmatters,- a REFERENCE to token-optimizer-mcp's own session state (never a copy of
it — see
docs/modules.md).
Run:
optiflow checkpoint "$ARGUMENTS"
After it runs, tell the user the checkpoint id it printed and that
/optiflow:restore (or /optiflow:restore <id>) will render it back later,
in a fresh session if needed.
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.
- 8d ago First seen · 34 lines · 38 tokens per session scan A 225fae2531e9
checkpoint is a command published in the GitHub repository kristijankopacevic/optiflow-mcp (0 stars, last pushed 16d ago), licensed MIT. It adds 38 tokens to every session and 356 once invoked, about $0.0002 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-31.
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.
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.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.