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/albedoweb/agmemWrote 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/albedoweb/agmem/plugin)<a href="https://agentmods.dev/plugins/albedoweb/agmem/plugin"><img src="https://agentmods.dev/badge/plugins/albedoweb/agmem/plugin/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/albedoweb/agmem/plugin"><img src="https://agentmods.dev/badge/plugins/albedoweb/agmem/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agmem 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": "agmem",
"displayName": "agmem — project memory",
"version": "0.1.0",
"description": "Persistent project memory for Claude Code — indexes your repo into local JSONL and auto-injects task-relevant context (BM25, no LLM calls, nothing leaves your machine)",
"author": {
"name": "Nikolay Fokin",
"url": "https://github.com/albedoweb"
},
"repository": "https://github.com/albedoweb/agmem",
"license": "Apache-2.0",
"keywords": ["memory", "context", "bm25", "local-first", "retrieval", "terraform", "python"]
}
What it installs
The manifest is a name and a version. 1 skill, 1 command, 1 hook travel with it, and installing the plugin installs all of them — 93 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.
- 1mo ago First seen · 14 lines scan A e8ed8064619a
agmem is a plugin published in the GitHub repository albedoweb/agmem (2 stars, last pushed 2mo 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
ownmem
Git-native project memory for AI coding agents, with deterministic local recall, evidence gates, and layered delivery that quotes, points, or abstains.
ownmem
Git-native project memory for AI coding agents, with deterministic local recall, evidence gates, and layered delivery that quotes, points, or abstains.
memtomem
Safe, explicit memory search and persistence workflows backed by the memtomem MCP server.
memtomem-automation
Opt-in prompt retrieval and write-time indexing automation for memtomem.
memX
memX: local-first semantic memory for coding agents. Native Claude Code lifecycle hooks.
memini
Persistent memory for AI coding agents via the memini memory service. 7 hooks, MCP tools, and skills that capture tool usage and inject prior context at session start and per prompt.