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/samrusani/AliceMemoryWrote 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/samrusani/alicememory/alice-memory)<a href="https://agentmods.dev/plugins/samrusani/alicememory/alice-memory"><img src="https://agentmods.dev/badge/plugins/samrusani/alicememory/alice-memory/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/samrusani/alicememory/alice-memory"><img src="https://agentmods.dev/badge/plugins/samrusani/alicememory/alice-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
alice-memory 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 13d 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": "alice-memory",
"version": "0.20.0",
"description": "Local-first memory for Claude Code: an MCP server and a SessionStart brief on one SQLite file.",
"author": {"name": "Alice Memory", "url": "https://alicememory.com"},
"homepage": "https://alicememory.com",
"repository": "https://github.com/samrusani/AliceMemory",
"license": "MIT",
"userConfig": {
"data_dir": {
"type": "string",
"title": "Alice data directory",
"description": "Absolute path, or ~/..., of the folder holding memory.db. Use the same folder as your other hosts.",
"default": "~/.alice",
"required": false
}
}
}
What it installs
The manifest is a name and a version. 1 hook, 1 MCP server travel with it, and installing the plugin installs all of 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.
- 13d ago Changed f7cd62457950
- 14d ago Changed 1d5df8c61a3c
- 16d ago First seen · 19 lines scan A 89e1eb969425
alice-memory is a plugin published in the GitHub repository samrusani/AliceMemory (4 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-09-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).
remnic
Universal memory for AI agents — automatic recall, observation, and cross-agent knowledge sharing.
plur
Persistent, local-first shared memory for AI agents. Corrections, preferences, and conventions persist across sessions, tools, and machines — stored as plain YAML on your disk, with zero-cost local search.
ourmem
Persistent memory for Claude Code — memories survive across sessions, projects, and machines.
strata
Persistent memory for AI assistants — runs locally on your machine. Remember every decision, debugging session, and architecture debate across sessions. One MCP server, zero cloud dependencies, works on a Raspberry Pi.
mnemoverse-memory
Persistent memory for AI agents, shared across tools: write a memory in one MCP client, recall it in another. OAuth sign-in, no API key to paste.