vector-memory-mcp: Command for Claude Code

.claude/commands/mem/get.md

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

A command for retrieving one saved memory using its numeric ID and displaying its full content and details.

In plain words
What is it for?
Use it when another command or search result gives you a memory ID that you want to read in full.
Why use it?
It provides a direct way to inspect a known entry without searching through all saved memories.

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/get.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:get

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/xsaven/vector-memory-mcp/get"><img src="https://agentmods.dev/badge/commands/xsaven/vector-memory-mcp/get.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 700 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.00008 $0.00700
Opus 5.5 $0.00003 $0.00280
Sonnet 5.5 $0.00002 $0.00140
Haiku 4.5 $0.00001 $0.00070

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

Security

Grade A, and why

mem:get 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/get.md · 75 lines

How it starts

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

Role

Memory retrieval utility that fetches and displays full content of a specific memory by ID.

Workflow step1

STEP 1 - Parse Arguments for Memory ID

  • format-1: /mem:get 15 → get memory by ID
  • format-2: /mem:get id=15 → explicit parameter
  • validate: IF(STORE-GET($RAW_INPUT) is empty or not a number) → Display: "Error: Memory ID required" → Display: "Usage: /mem:get {id}" → SKIP(No ID provided) → END-IF

Input

STORE-AS($RAW_INPUT = $ARGUMENTS) STORE-AS($MEMORY_ID = {numeric ID extracted from $RAW_INPUT})

Workflow step2

STEP 2 - Fetch Memory by ID

  • fetch: mcp__vector-memory__get_by_memory_id('{memory_id: STORE-GET($MEMORY_ID)}')
  • store: STORE-AS($MEMORY = memory object or null)

Workflow step3

STEP 3 - Handle Memory Not Found

  • check: IF(STORE-GET($MEMORY) is null) → Display: "Memory #{id} not found." → Suggest: "Use /mem:list to see available memories" → Suggest: "Use /mem:search to find by content" → END-IF

Workflow step4

STEP 4 - Display Full Memory Content

  • header: Display: "--- Memory #{id} ---"
  • meta: Display: "Category: {category}" → Display: "Tags: {tags}" → Display: "Created: {created_at}" → Display: "Updated: {updated_at}" → Display: "Access count: {access_count}"
  • divider: Display: "---"
  • content: Display: "{full_content}"
  • divider-end: Display: "---"
  • actions: Display: "Actions:" → Display: " /mem:cleanup id={id} → delete this memory" → Display: " /mem:search \"{first_words}\" → find similar"

Output format

Memory display format

  • --- Memory #15 ---
  • Category: code-solution
  • Tags: php, laravel, auth
  • Created: 2025-11-20 14:30:00
  • Access count: 5

  • {full memory content here}
  • Actions:
  • /mem:cleanup id=15 → delete
  • /mem:search "keywords" → find similar

Read the full file on GitHub · 75 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 · 75 lines · 8 tokens per session scan A 91484f49f252

Subscribe to this mod's changes

mem:get is a command published in the GitHub repository Xsaven/vector-memory-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 700 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:get compared with commands from other repositories

mem:get next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
mem:getXsaven/vector-memory-mcpCommand08mo agoMITA8Claude 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