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/restore)<a href="https://agentmods.dev/commands/kristijankopacevic/optiflow-mcp/restore"><img src="https://agentmods.dev/badge/commands/kristijankopacevic/optiflow-mcp/restore/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/restore"><img src="https://agentmods.dev/badge/commands/kristijankopacevic/optiflow-mcp/restore.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.00029 | $0.00312 |
| Opus 5 | $0.00015 | $0.00156 |
| Sonnet 5 | $0.00006 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
restore 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
Render an optiflow session-handoff checkpoint and show it to the user verbatim so they can resume work — this is meant to be pasted/read at the start of a fresh session after a compaction or a prior session ended.
The real command is /optiflow:restore (plugin-namespaced — there is no
bare /restore). With no argument it renders the MOST RECENT checkpoint in
the current project's .optiflow/checkpoints/; with an argument, it matches
either a full checkpoint id or a bare session id prefix.
Run:
optiflow checkpoint --restore "$ARGUMENTS"
If it prints "No checkpoints found yet," say so plainly and suggest running
/optiflow:checkpoint [notes] first — this is a normal state for a project
that has never compacted/ended a session under optiflow, not an error.
Note on the token-optimizer state reference the output includes: it is a REFERENCE (a file path + the sessionId key to look it up under), not a copy of token-optimizer-mcp's own session content — resolving it may show "did not exist at checkpoint time" if token-optimizer wasn't tracking that session, which is an honest, expected outcome, not a bug.
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 · 30 lines · 29 tokens per session scan A 42309964f088
restore is a command published in the GitHub repository kristijankopacevic/optiflow-mcp (0 stars, last pushed 17d ago), licensed MIT. It adds 29 tokens to every session and 312 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-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.