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.
git clone --depth 1 https://github.com/jagoff/memoWrote 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/plugins/jagoff/memo/memo)<a href="https://agentmods.dev/plugins/jagoff/memo/memo"><img src="https://agentmods.dev/badge/plugins/jagoff/memo/memo/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/plugins/jagoff/memo/memo"><img src="https://agentmods.dev/badge/plugins/jagoff/memo/memo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memo 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 1mo 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.
What it actually says
{
"name": "memo",
"description": "Local MCP memory for AI agents — MLX on Apple Silicon or CPU sentence-transformers on Linux/Ubuntu, sqlite-vec store, markdown-on-disk in your Obsidian vault. Zero Ollama, zero cloud APIs.",
"version": "4.16.0",
"author": {
"name": "Fernando Ferrari",
"email": "[email protected]",
"url": "https://github.com/jagoff"
},
"homepage": "https://github.com/jagoff/memo",
"repository": "https://github.com/jagoff/memo",
"license": "MIT",
"keywords": ["memory", "mcp", "mlx", "obsidian", "rag", "agents", "local-first"]
}
What it installs
The manifest is a name and a version. 4 skills, 1 command, 4 hooks, 1 MCP server travel with it, and installing the plugin installs all of them — 111 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill memo A 68 tokens
- Skill remotion-render A 9 tokens
- Skill remotion-create A 10 tokens
- Skill remotion-best-practices A 12 tokens
- Command memo A 12 tokens
- Hook SessionStart A not measured
- Hook Stop A not measured
- Hook UserPromptSubmit A not measured
- Hook PreCompact A not measured
- MCP server memo A not measured
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed d9fa9e6b4522
- 1mo ago First seen · 15 lines scan A 4bafe4f3db9b
memo is a plugin published in the GitHub repository jagoff/memo (22 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
iai-memory
Persistent local memory for your assistant: every turn captured verbatim, relevant memory injected at session start and before each turn, and fourteen memory tools over MCP. Requires the iai-pme package (pip install iai-pme).
memora
Persistent semantic memory for Claude Code — auto-injects relevant context at session start, captures git commits, test results, and research via hooks, and provides 30+ MCP tools for memory management.
hypermnesia-mcp
Cortex — persistent memory for Claude Code that remembers across sessions automatically. Install and forget. Scientific retrieval backed by 97 published references. (Renamed from the 'cortex' plugin to match the PyPI/MCP-registry identity.).
openclaw
OpenClaw AI assistant integration. Chat, manage sessions, access memory, and run async tasks through your OpenClaw instance.
perenna
A lightweight, Git-backed permanent memory for AI agents.
papi
Persistent project management inside your AI coding tool. PAPI plans what to build next, tracks every decision, and keeps projects coherent across sessions — so a new session starts where the last one left off instead of from nothing.