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/xsaven/vector-memory-mcp/listgit clone --depth 1 https://github.com/Xsaven/vector-memory-mcpWhat 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.00008 | $0.00561 |
| Opus 5 | $0.00004 | $0.00280 |
| Sonnet 5 | $0.00002 | $0.00112 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
mem:list 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 yesterday.
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
Input
STORE-AS($RAW_INPUT = $ARGUMENTS) STORE-AS($LIST_LIMIT = {numeric limit extracted from $RAW_INPUT, default 10})
Role
Simple memory listing utility that displays recent memories chronologically with previews and metadata.
Workflow step1
STEP 1 - Parse Arguments for Limit
format: /mem:list OR /mem:list limit=20extract: STORE-AS($LIMIT = {parse limit from $RAW_INPUT, default 10, max 50})validate: IF($LIMIT > 50) → Set $LIMIT = 50 (max allowed)
Workflow step2
STEP 2 - Fetch Recent Memories
fetch: mcp__vector-memory__list_recent_memories('{limit: STORE-GET($LIMIT)}')store: STORE-AS($MEMORIES = recent memories array)
Workflow step3
STEP 3 - Handle No Memories
check: IF(STORE-GET($MEMORIES) is empty) → Display: "No memories stored yet." → Suggest: "Use /mem:store to add your first memory" → END-IF
Workflow step4
STEP 4 - Format and Display
header: Display: "--- Recent Memories ({count}) ---"list: FOREACH(memory in STORE-GET($MEMORIES)) → Display: "#{id} [{category}] {created_at}" → Display: " {content_preview} (first 80 chars)..." → Display: " Tags: {tags}" → END-FOREACHfooter: Display: "Use /mem:get {id} to view full content"
Output format
Display format for memory list
- --- Recent Memories (10) ---
- #{id} [{category}] 2025-11-22
- Content preview here...
- Tags: php, laravel, auth
- Use /mem:get {id} to view full content
Usage examples
Command usage patterns
- /mem:list → last 10 memories
- /mem:list limit=20 → last 20 memories
- /mem:list limit=50 → maximum allowed
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.
- yesterday First seen · 62 lines · 8 tokens per session scan A 00b2e9bb0c35
mem:list is a command published in the GitHub repository Xsaven/vector-memory-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 561 once invoked, about $0.0000 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-09-01.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.