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/compact-continue)<a href="https://agentmods.dev/commands/kristijankopacevic/optiflow-mcp/compact-continue"><img src="https://agentmods.dev/badge/commands/kristijankopacevic/optiflow-mcp/compact-continue.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.1 | $0.00029 | $0.00416 |
| Opus 5 | $0.00015 | $0.00208 |
| Sonnet 5 | $0.00006 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
compact-continue 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 7d 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
Run optiflow's combined checkpoint-and-restore handoff and show the result to the user.
The real command is /optiflow:compact-continue (plugin-namespaced — there
is no bare /compact-continue; see docs/modules.md for how a user could
add one under ~/.claude/commands/ themselves if they want it, which this
plugin does not do on their behalf). It does exactly two things, in order:
- Saves a new checkpoint right now — same as
/optiflow:checkpoint "$ARGUMENTS"— capturing the current git branch/HEAD, cwd, a reference to token-optimizer-mcp's own session state, and$ARGUMENTS(if any) as the checkpoint'sdecisions[]entry. - Immediately renders that checkpoint back as the same resume-ready markdown
/optiflow:restoreproduces (capped at 10,000 chars by default).
Run:
optiflow checkpoint "$ARGUMENTS"
optiflow checkpoint --restore
Important — this command does NOT trigger compaction. It only prepares
for one (or for a session ending): it snapshots state and shows the user
what a fresh session would see if it resumed from this checkpoint right now.
If the user's actual goal is to compact or end the session, they still need
to do that themselves (e.g. /compact, or simply ending the session) — this
command is the "make sure a checkpoint exists and looks right before that
happens" step, not a replacement for it.
Tell the user the checkpoint id from step 1, then show the rendered markdown from step 2 so they can confirm it captures what they'd want to resume with.
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.
- 7d ago First seen · 38 lines · 29 tokens per session scan A b68b895069d6
compact-continue is a command published in the GitHub repository kristijankopacevic/optiflow-mcp (0 stars, last pushed 15d ago), licensed MIT. It adds 29 tokens to every session and 416 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.