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.
npx agentmods add commands/sdsrss/claude-mem-lite/memgit clone --depth 1 https://github.com/sdsrss/claude-mem-liteWrote 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/sdsrss/claude-mem-lite/mem)<a href="https://agentmods.dev/commands/sdsrss/claude-mem-lite/mem"><img src="https://agentmods.dev/badge/commands/sdsrss/claude-mem-lite/mem.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 | $0.00016 | $0.00590 |
| Opus 5 | $0.00008 | $0.00295 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
mem 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 5d 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
Memory
Search and browse your project memory efficiently.
Quick Commands
/mem search <query>— Search all memories (FTS5 full-text search)/mem recent [n]— Show recent N observations (default 5)/mem recall <file>— History for a file before editing/mem timeline <id>— Browse timeline around an observation/mem save <text>— Save a manual memory/note/mem stats— Show memory statistics/mem cleanup— Scan and interactively purge stale data/mem cleanup [N]d— Purge stale data older than N days (e.g.cleanup 60d)/mem cleanup keep [N]d— Purge stale data but retain last N days (e.g.cleanup keep 14d)
Instructions
When the user invokes /mem, parse their intent:
/mem search <query>→ runnode ${CLAUDE_PLUGIN_ROOT}/cli.mjs search <query>via Bash/mem recentor/mem recent 20→ runnode ${CLAUDE_PLUGIN_ROOT}/cli.mjs recent [N]via Bash/mem recall <file>→ runnode ${CLAUDE_PLUGIN_ROOT}/cli.mjs recall <file>via Bash/mem timeline <id>→ runnode ${CLAUDE_PLUGIN_ROOT}/cli.mjs timeline --anchor <id>via Bash/mem save <text>→ callmem_saveMCP tool with the text as content/mem stats→ runnode ${CLAUDE_PLUGIN_ROOT}/cli.mjs statsvia Bash/mem get <ids>→ runnode ${CLAUDE_PLUGIN_ROOT}/cli.mjs get <ids>via Bash/mem cleanup→ runmem_maintain(action="scan"), report pending purge count and stale items to user, ask for confirmation, then runmem_maintain(action="execute", operations=["purge_stale"])if confirmed/mem cleanup Nd(e.g.60d) → same as above but useretain_days=Nto only purge items older than N days/mem cleanup keep Nd(e.g.keep 14d) → same as above withretain_days=N/mem <query>(no subcommand) → treat as search, runnode ${CLAUDE_PLUGIN_ROOT}/cli.mjs search <query>via Bash
Use Bash commands first. For detailed data, use node ${CLAUDE_PLUGIN_ROOT}/cli.mjs get <id> via Bash.
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.
- 5d ago First seen · 39 lines · 16 tokens per session scan A 07adcf705b38
mem is a command published in the GitHub repository sdsrss/claude-mem-lite (56 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 590 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
session-save
Save the current session state — decisions, modified files, current status, and next steps — to a handoff file for later resume.
presence-reset
Wipe presence state for the current project, all projects, or specific subsystems. Asks for confirmation before destructive action.
clear
Context-clearing command. Provides a seamless transition across session boundaries. Target: under 30 seconds.
sc-detail
Throughline の退避済みターン(L2 本文 + L3 ツール入出力)を時刻で復元する.
scope
Search your Claude Code session history (full-text, always fresh).
tl
Throughline の UserPromptSubmit hook が /tl を検出し、バトン(現セッション ID)を保存しました。.