A maintenance command for a memory database and a registry of tool resources. It scans for duplicates, stale or broken items, and items that may need cleanup, compression, or a boost.

Use it for periodic memory cleanup, duplicate merging, decay and boosting, compression of old observations, and registry maintenance.

It helps keep stored agent memory and tool records organized after imports or when search results become noisy. Purging old data requires explicit confirmation.

update — Command for Claude Code by sdsrss/claude-mem-lite

Install

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.

Claude Code

/plugin marketplace add sdsrss/claude-mem-lite

Claude Code

/plugin install claude-mem-lite

Made for: Claude Code.

Or install claude-mem-lite, the plugin that ships this one along with the rest of its 8 commands, 7 hooks, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sdsrss/claude-mem-lite/update/github.svg)](https://agentmods.dev/commands/sdsrss/claude-mem-lite/update)

Your own site

<a href="https://agentmods.dev/commands/sdsrss/claude-mem-lite/update"><img src="https://agentmods.dev/badge/commands/sdsrss/claude-mem-lite/update/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sdsrss/claude-mem-lite/update"><img src="https://agentmods.dev/badge/commands/sdsrss/claude-mem-lite/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 686 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00014	$0.00686
Opus 5.5	$0.00006	$0.00274
Sonnet 5.5	$0.00003	$0.00137
Haiku 4.5	$0.00001	$0.00069

Measured 2d ago against content hash 7563fd6490e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

update 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 2d 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.

commands/update.md · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory Maintenance

Run intelligent maintenance on the memory database.

Usage

/claude-mem-lite:update — Run full maintenance cycle

Instructions

When the user invokes /claude-mem-lite:update, perform the following maintenance cycle:

Phase 1: Memory Maintenance

Run each command below via Bash; the CLI reaches the maintenance operations whether or not their MCP tools are in your tool list.

Run node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain scan to analyze maintenance candidates
Report scan results to the user (duplicates, stale items, broken items, boostable items, pending purge items)
If pending purge items > 0: first run the purge command below without --confirm: it prints how many rows it would delete and deletes nothing. If that count is 0, tell the user nothing is old enough to purge yet and go on to the next step. Otherwise report that count to the user and ask for confirmation. If confirmed, run node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain execute --ops purge_stale --confirm. --confirm is required: without it the command prints a dry-run preview and deletes nothing while still succeeding, so you would report a purge that never happened. User may optionally add --retain-days N (default 30, allowed range 7–365) to both runs to control how many days of data to keep; the CLI rejects a value outside that range, so tell the user instead of substituting the default. Do NOT purge without explicit user confirmation. The purge comes before the next step on purpose: decay there queues more rows for purge, and those wait for a later run instead of joining the purge the user approved.
Run node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain execute to apply safe automatic changes — with no --ops it runs the default set: cleanup, decay, boost, then demote_pinned (left out when CLAUDE_MEM_SKIP_DEMOTE_PINNED=1)
If duplicates were found in scan, review them and run node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain execute --ops dedup --merge-ids keepId:removeId,... — keep the more important/recent observation in each pair. Groups are comma-separated and the first id in each is kept (10:11,20:21:22). For pairs similar enough to merge without review the scan prints a ready-to-run command after Ready-to-use:; run it as printed. Judge each pair under Needs review: from the two lines the scan prints below it; do not read them with get: that counts as an access and can raise a row's importance
Run node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" compress --execute for old low-value observations (without --execute it only previews)

Read the full file on GitHub · 35 lines

Changes

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.

2d ago Changed 7563fd6490e5
3d ago Changed · +3 lines 1533cd744183
1mo ago Changed · -7 lines · -7 tokens per session 79a3572e04d5
1mo ago First seen · 39 lines · 21 tokens per session scan A 874080844553

Subscribe to this mod's changes

update is a command published in the GitHub repository sdsrss/claude-mem-lite (67 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 686 once invoked, about $0.0001 per session on Opus 5.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.

Claude Code Memory and context fts5 hooks mcp persistence

update

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Memory Maintenance

Usage

Instructions

Phase 1: Memory Maintenance

What this file has done since we first saw it

Other commands, from other repositories

session-save

drift-detect

wrap-up

clear

sync

memory-diff