Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add lossless-claude/lcm/plugin install lcmWrote 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/lossless-claude/lcm/lcm-curate)<a href="https://agentmods.dev/commands/lossless-claude/lcm/lcm-curate"><img src="https://agentmods.dev/badge/commands/lossless-claude/lcm/lcm-curate.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.00020 | $0.00371 |
| Opus 5 | $0.00010 | $0.00186 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
lcm-curate 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
/lcm-curate
Run the full memory curation pipeline: import, compact, and promote.
Instructions
Run the following commands sequentially via Bash. Always use --verbose on import and promote by default:
lcm import --verbose && lcm compact && lcm promote --verbose
If lcm is not on PATH (marketplace install), use the plugin-relative binary instead:
node "${CLAUDE_PLUGIN_ROOT}/lcm.mjs" import --verbose && node "${CLAUDE_PLUGIN_ROOT}/lcm.mjs" compact && node "${CLAUDE_PLUGIN_ROOT}/lcm.mjs" promote --verbose
Options
Pass user-specified flags through to the commands that support them:
--all— Process all projects (default: current project only); applies to all three commands--no-verbose— Suppress verbose output (verbose is on by default)--dry-run— Preview without writing; applies to all three commands
For example:
/lcm-curate --all→lcm import --all --verbose && lcm compact --all && lcm promote --all --verbose/lcm-curate --dry-run→lcm import --dry-run --verbose && lcm compact --dry-run && lcm promote --dry-run --verbose/lcm-curate --no-verbose→lcm import && lcm compact && lcm promote
The pipeline stops on the first failure and reports the result.
Display the output verbatim.
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 · 40 lines · 20 tokens per session scan A 7deb34fa3a9b
lcm-curate is a command published in the GitHub repository lossless-claude/lcm (24 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 371 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-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.
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.