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 xlfish233/mem-vid-mcp --skill memvid-coregit clone --depth 1 https://github.com/xlfish233/mem-vid-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/xlfish233/mem-vid-mcp/memvid-core)<a href="https://agentmods.dev/skills/xlfish233/mem-vid-mcp/memvid-core"><img src="https://agentmods.dev/badge/skills/xlfish233/mem-vid-mcp/memvid-core/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/xlfish233/mem-vid-mcp/memvid-core"><img src="https://agentmods.dev/badge/skills/xlfish233/mem-vid-mcp/memvid-core.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.00056 | $0.00916 |
| Opus 5 | $0.00028 | $0.00458 |
| Sonnet 5 | $0.00011 | $0.00183 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
memvid-core 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 10d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memvid Memory Skill
This skill enables natural memory storage and retrieval using a dual-memory architecture.
Memory Scopes
Project Memory (.memvid_data/)
Stores project-specific knowledge:
- Code architecture decisions: "This project uses FastAPI for APIs"
- Bug reports: "Bug in auth.py line 42"
- Technical implementation: "We use MemvidMemory class for storage"
- Project configuration: "Dependencies managed via pyproject.toml"
User Memory (~/memvid_data/)
Stores personal preferences:
- Coding preferences: "I prefer pytest over unittest"
- Style preferences: "I like clean code with type hints"
- Tool preferences: "I use VS Code for development"
- General knowledge: "I always document functions with docstrings"
Automatic Classification
The system uses semantic similarity to auto-classify memories:
- Compares content against project and user examples
- Assigns to scope with higher similarity
- Falls back to user memory if confidence < 0.65
Commands
memvid:store
Store a new memory with automatic scope detection.
Trigger patterns:
- "remember that this project uses FastAPI"
- "note that I prefer pytest"
- "for future reference: bug in line 42"
Action: Call memvid_store tool with:
{
"content": "<extracted content>",
"scope": "auto"
}
Response format: "Stored in [project/user] memory: [brief summary]. (ID: abc-123)"
memvid:recall
Search both memories and return merged results.
Trigger patterns:
- "what did I say about testing?"
- "recall memories about authentication"
- "do you remember my coding preferences?"
Action: Call memvid_query tool with:
{
"query": "<extracted query>",
"limit": 10
}
Response format: Present results naturally: "Based on your memories:
- [Project] This project uses FastAPI for REST APIs
- [User] You prefer pytest over unittest"
memvid:forget
Delete a memory by ID.
Trigger patterns:
- "forget memory abc-123"
- "delete that memory about authentication"
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.
- 10d ago First seen · 132 lines · 56 tokens per session scan A 624133c26288
memvid-core is a skill published in the GitHub repository xlfish233/mem-vid-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 56 tokens to every session and 916 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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.