vector-memory-mcp: Command for Claude Code

.claude/commands/mem/cleanup.md

mem:cleanup is a command for Claude Code from Xsaven/vector-memory-mcp. It costs 11 tokens per session (1,276 once invoked), scanned A, original, MIT.

A command for removing saved memories by age, storage limit, or specific ID. It previews or confirms destructive actions before deletion.

In plain words
What is it for?
Use it to remove old memories, keep only a chosen number of recent entries, or delete one or more selected memories.
Why use it?
It helps control an expanding memory store while reducing the risk of deleting information accidentally.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is Xsaven/vector-memory-mcp's own configuration. It tells Claude Code how to work on vector-memory-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vector-memory-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Xsaven/vector-memory-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Xsaven/vector-memory-mcp/master/.claude/commands/mem/cleanup.md
Clone the repo
git clone --depth 1 https://github.com/Xsaven/vector-memory-mcp

Made for: Claude Code.

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.

agentmods badge for mem:cleanup

README.md
[![agentmods](https://agentmods.dev/badge/commands/xsaven/vector-memory-mcp/cleanup/github.svg)](https://agentmods.dev/commands/xsaven/vector-memory-mcp/cleanup)
Your own site
<a href="https://agentmods.dev/commands/xsaven/vector-memory-mcp/cleanup"><img src="https://agentmods.dev/badge/commands/xsaven/vector-memory-mcp/cleanup/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.

agentmods 80×15 button for mem:cleanup

Your own site · 80×15
<a href="https://agentmods.dev/commands/xsaven/vector-memory-mcp/cleanup"><img src="https://agentmods.dev/badge/commands/xsaven/vector-memory-mcp/cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,276 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.01276
Opus 5.5 $0.00004 $0.00510
Sonnet 5.5 $0.00002 $0.00255
Haiku 4.5 $0.00001 $0.00128

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

Security

Grade A, and why

mem:cleanup 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 2mo 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.

.claude/commands/mem/cleanup.md · 97 lines

How it starts

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

Role

Memory cleanup utility that handles bulk deletion by age/count or specific ID deletion. All destructive operations require explicit confirmation.

Input

STORE-AS($RAW_INPUT = $ARGUMENTS) STORE-AS($CLEANUP_PARAMS = {cleanup parameters extracted from $RAW_INPUT: days_old, max_to_keep, or memory_id})

Workflow step1

STEP 1 - Parse $RAW_INPUT for Operation Type

  • format-1: /mem:cleanup → preview default cleanup (30 days, keep 1000)
  • format-2: /mem:cleanup days=60 → cleanup older than 60 days
  • format-3: /mem:cleanup max_to_keep=500 → keep only 500 most recent
  • format-4: /mem:cleanup id=15 → delete specific memory
  • format-5: /mem:cleanup ids=15,16,17 → delete multiple specific
  • detect: STORE-AS($MODE = {detect mode: bulk|single|multi from STORE-GET($RAW_INPUT)})
  • extract-ids: STORE-AS($DELETE_IDS = {extract id/ids from STORE-GET($RAW_INPUT) if present})
  • extract-params: Use STORE-GET($CLEANUP_PARAMS) for days_old, max_to_keep values

Workflow step2

STEP 2 - Handle Single ID Delete

  • check: IF(STORE-GET($MODE) === "single") → Use ID from STORE-GET($DELETE_IDS) → mcp__vector-memory__get_by_memory_id('{memory_id: {id}}') → STORE-AS($TARGET = memory to delete) → Display: "--- Memory to Delete ---" → Display: "ID: {id}" → Display: "Category: {category}" → Display: "Content: {content_preview}" → Display: "Tags: {tags}" → Display: "" → Prompt: "DELETE this memory? This cannot be undone. (yes/no)" → END-IF

Workflow step3

STEP 3 - Handle Multiple IDs Delete

  • check: IF(STORE-GET($MODE) === "multi") → Use IDs array from STORE-GET($DELETE_IDS) → ForEach ID: fetch memory preview → Display: "--- Memories to Delete ({count}) ---" → ForEach: "#{id} [{category}] {preview}" → Display: "" → Prompt: "DELETE all {count} memories? This cannot be undone. (yes/no)" → END-IF

Read the full file on GitHub · 97 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.

  1. 2mo ago First seen · 97 lines · 11 tokens per session scan A 2247e6b33e65

Subscribe to this mod's changes

mem:cleanup is a command published in the GitHub repository Xsaven/vector-memory-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 1,276 once invoked, about $0.0000 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-09-01.

Related

mem:cleanup compared with commands from other repositories

mem:cleanup next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
mem:cleanupXsaven/vector-memory-mcpCommand08mo agoMITA11Claude Code
minutes-ideassilverstein/minutesCommand1.6kyesterdayMITA48Claude Code, OpenCode
learnReflexioAI/claude-smartCommand7913d agoApache-2.0A14Claude Code
memory-storeverygoodplugins/mcp-automemCommand66yesterdayMITA10Claude Code
analyze-contextRohiRIK/OpenLtmCommand298d agoMITA39Claude Code
cc-memoryTheLobbi/claudeCommand217d agoMITA0Claude Code
lians-recallLians-ai/LiansCommand175d agoApache-2.0A19Claude Code