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-import)<a href="https://agentmods.dev/commands/lossless-claude/lcm/lcm-import"><img src="https://agentmods.dev/badge/commands/lossless-claude/lcm/lcm-import.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.00013 | $0.00460 |
| Opus 5 | $0.00006 | $0.00230 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
lcm-import 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-import
Import Claude Code session transcripts into lcm memory.
Instructions
Run the following command via Bash:
lcm import
If lcm is not on PATH (marketplace install), use the plugin-relative binary instead:
node "${CLAUDE_PLUGIN_ROOT}/lcm.mjs" import
Options
If the user specifies options, append them to the command:
--all— Import all projects instead of just the current project--verbose— Show per-session details--dry-run— Preview without writing--replay— Re-import all sessions in chronological order and compact each one immediately, threading context between sessions to build a temporal summary DAG. Use to rebuild memory from scratch.
For example:
/lcm-import --all→lcm import --all/lcm-import --all --verbose→lcm import --all --verbose/lcm-import --dry-run→lcm import --dry-run/lcm-import --replay→lcm import --replay
Display the output verbatim.
After importing, suggest running lcm compact to summarize the imported sessions (or lcm compact --all if --all was used with import). Note: when --replay is used, compaction is performed inline — no separate compact step is needed.
When to use
- After installing lcm for the first time (backfill existing sessions)
- After a session that failed to ingest (hook error, daemon down)
- To recover lost conversations
- After upgrading lcm (ensure all sessions are captured)
Commands
lcm import— import current project's sessionslcm import --all— import all projectslcm import --verbose— show per-session detailslcm import --dry-run— preview without writinglcm compact --all— summarize all uncompacted sessions (run after import)
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 · 57 lines · 13 tokens per session scan A b0457ce9fbdf
lcm-import is a command published in the GitHub repository lossless-claude/lcm (24 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 460 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.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.