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/unvulcanised-watercress762/mem9Wrote 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/unvulcanised-watercress762/mem9/claude-plugin)<a href="https://agentmods.dev/plugins/unvulcanised-watercress762/mem9/claude-plugin"><img src="https://agentmods.dev/badge/plugins/unvulcanised-watercress762/mem9/claude-plugin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mem9 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 7d 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": "mem9",
"version": "0.2.0",
"description": "Persistent cloud memory for Claude Code. Auto-loads memories on session start, auto-saves on stop, with on-demand store/recall skills.",
"author": {
"name": "mem9-ai"
},
"repository": "https://github.com/mem9-ai/mem9-claude-plugin",
"license": "Apache-2.0"
}
What it installs
The manifest is a name and a version. 3 skills, 3 hooks travel with it, and installing the plugin installs all of them — 92 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 7d ago First seen · 11 lines scan A d841739ab8ab
mem9 is a plugin published in the GitHub repository unvulcanised-watercress762/mem9 (3 stars, last pushed 2d ago), licensed Apache-2.0. 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-31.
Other plugins, from other repositories
claude-mem-cursor
Persistent memory for Cursor. Hooks ingest tool use; MCP searches past sessions. Works with a local worker or a remote cmem.ai worker, and a local host-login observer or remote inference.
claude-mem-grok-bot
Persistent memory for Grok Bot. No host hooks: transcript watcher plus MCP. Local worker with host-login observer, or remote cmem.ai. Install without Cursor.
claude-mem
Memory compression system for Claude Code - persist context across sessions.
claude-mem-cowork
Claude-Mem for Cowork: captures tool use via hooks, streams fragments to cmem.ai (Pro runs the observer), and injects observations back into new sessions and spawned agents.
agent-orchestration
Multi-agent system optimization, agent improvement workflows, and context management.
code-refactoring
Code cleanup, refactoring automation, and technical debt management with context restoration.