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 skills add aeriondyseti/vector-memory-mcp --skill vector-memory-usagegit clone --depth 1 https://github.com/aeriondyseti/vector-memory-mcpWrote 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/skills/aeriondyseti/vector-memory-mcp/vector-memory-usage)<a href="https://agentmods.dev/skills/aeriondyseti/vector-memory-mcp/vector-memory-usage"><img src="https://agentmods.dev/badge/skills/aeriondyseti/vector-memory-mcp/vector-memory-usage/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.
<a href="https://agentmods.dev/skills/aeriondyseti/vector-memory-mcp/vector-memory-usage"><img src="https://agentmods.dev/badge/skills/aeriondyseti/vector-memory-mcp/vector-memory-usage.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00102 | $0.02225 |
| Opus 5.5 | $0.00041 | $0.00890 |
| Sonnet 5.5 | $0.00020 | $0.00445 |
| Haiku 4.5 | $0.00010 | $0.00222 |
Grade A, and why
vector-memory-usage 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vector Memory Usage
The vector memory system provides semantic memory storage shared across every project. Memories persist across sessions and are retrieved via semantic search — meaning queries find relevant memories by meaning, not just keyword matching.
Global Storage Model
The vector-memory MCP server stores all memories in a single global SQLite database (~/.vector-memory/memories.db), shared by every project on the machine. Each memory is automatically tagged with the project (the working directory) it was stored from — no per-repo database, nothing to commit to version control.
- Storing: memories are stamped with the current project automatically. Only pass an explicit
projectto file a memory under a different project. - Searching: by default, search covers all projects; results from the current project rank slightly higher, and every result carries its project path. Pass
scope: "project"when the query is clearly specific to the current repo (cuts cross-project noise), or an explicit project path to search another repo's memories. - Migrating: repos with a legacy
.vector-memory/directory can be imported into the global store withbunx @aeriondyseti/vector-memory-mcp consolidate(see the README). If a repo still has.vector-memory/in version control, remove it and add.vector-memory/to.gitignore.
A repo-local database is still available via --db-file or VECTOR_MEMORY_DB_PATH for special cases.
When to Proactively Search Memories
Search memories BEFORE making decisions or assumptions. The cost of an unnecessary search is low; the cost of missing relevant context is high.
Mandatory Search Triggers
- Architectural decisions — before choosing a library, pattern, or approach, search for prior decisions on the same topic
- Debugging unfamiliar code — search for implementation notes, known issues, or past resolutions
- Starting a new task — search for relevant context, prior attempts, or related decisions
- Referential ambiguity — when the user says "the project", "that bug", "last time", "as we discussed", search to resolve the reference
- Repeated patterns — when implementing something similar to past work, search for the established pattern
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.
- 11d ago Changed · +24 lines 1c40a2fe6ace
- 20d ago Changed ba8b1b557e82
- 1mo ago First seen · 178 lines · 102 tokens per session scan A e06e1fdcdc32
vector-memory-usage is a skill published in the GitHub repository aeriondyseti/vector-memory-mcp (5 stars, last pushed 2d ago), licensed MIT. It adds 102 tokens to every session and 2,225 once invoked, about $0.0004 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.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.