Borrowing it
Nothing to install: this file belongs to lossless-claude/lcm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lossless-claude/lcm/main/.agents/skills/lcm-context/SKILL.mdgit clone --depth 1 https://github.com/lossless-claude/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/skills/lossless-claude/lcm/lcm-context)<a href="https://agentmods.dev/skills/lossless-claude/lcm/lcm-context"><img src="https://agentmods.dev/badge/skills/lossless-claude/lcm/lcm-context.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.01057 |
| Opus 5 | $0.00020 | $0.00528 |
| Sonnet 5 | $0.00008 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
lcm-context 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lcm Memory — Universal Agent Guide
Use the lcm CLI to retrieve and store project memory across sessions.
Install: npm install -g @lossless-claude/lcm
Memory is stored in SQLite (FTS5) and accessed via CLI commands or MCP tools.
Workflow
- Before Thinking: Run
lcm searchorlcm grepto recall past decisions and context. - After Implementing: Run
lcm storeto persist new decisions, patterns, or findings.
Commands
1. Search Memory (broad recall)
Retrieve relevant context across all past sessions using full-text search.
Use when:
- You need to recall past decisions, patterns, or architectural context
- Before performing any action, to check for relevant rules or preferences
- Your context does not contain information you need
Do NOT use when:
- The information is already present in your current context
- The query is about general knowledge, not project memory
lcm search "how was auth implemented"
lcm search "compaction architecture" --tags decision,architecture
lcm search "JWT token" --layers episodic
2. Grep Memory (exact match)
Search raw conversation transcripts by keyword or regex.
Use when:
- You need an exact keyword, error message, or function name from past sessions
- Search returned too many broad results and you need to narrow down
Do NOT use when:
- You need conceptual recall (use
lcm searchinstead)
lcm grep "socket.unref"
lcm grep "JWT" --scope summaries
lcm grep "ECONNREFUSED" --since 2026-03-20
3. Expand a Summary Node
Decompress a summary node from the DAG into its full source content.
Use when:
- A search or grep result references a summary nodeId and you need more detail
- Check with
lcm describe <nodeId>first to see if it's worth expanding (saves tokens)
lcm describe <nodeId> # check metadata first
lcm expand <nodeId> # decompress if relevant
lcm expand <nodeId> --depth 2 # deeper traversal
4. Store a Decision or Finding
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 · 136 lines · 41 tokens per session scan A ee27f50d1dc7
lcm-context is a skill published in the GitHub repository lossless-claude/lcm (24 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,057 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-30.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.