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/memseekai/memseekWrote 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/memseekai/memseek/claude-code)<a href="https://agentmods.dev/plugins/memseekai/memseek/claude-code"><img src="https://agentmods.dev/badge/plugins/memseekai/memseek/claude-code/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/memseekai/memseek/claude-code"><img src="https://agentmods.dev/badge/plugins/memseekai/memseek/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memseek-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 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": "memseek-memory",
"version": "0.2.0",
"description": "Durable, provenance-aware project memory for Claude Code.",
"author": {
"name": "Memseek"
},
"homepage": "https://github.com/memseekai/memseek",
"repository": "https://github.com/memseekai/memseek",
"userConfig": {
"MEMSEEK_URL": {
"type": "string",
"title": "Memseek service URL",
"description": "Base URL supplied by your Memseek administrator, without a trailing slash (for example, https://memory.example.com).",
"required": true,
"default": "http://127.0.0.1:8000"
},
"MEMSEEK_API_KEY": {
"type": "string",
"title": "Memseek workspace key",
"description": "Workspace key supplied by your Memseek administrator. Claude Code stores this as a sensitive value.",
"sensitive": true,
"required": true
},
"MEMSEEK_CAPTURE_MODE": {
"type": "string",
"title": "Conversation capture",
"description": "Controls new writes, not recall. conversation saves exact user and assistant chat messages automatically; explicit saves only when you ask Claude to remember; off tells Claude to make no new writes. Existing memory remains readable in every mode.",
"required": true,
"default": "conversation"
}
},
"keywords": [
"memory",
"context",
"mcp",
"claude-code"
]
}
What it installs
The manifest is a name and a version. 5 skills, 5 hooks, 1 MCP server travel with it, and installing the plugin installs all of them — 118 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill memseek-feedback A 23 tokens
- Skill memseek-status A 24 tokens
- Skill memseek-remember A 24 tokens
- Skill memseek-explain A 25 tokens
- Skill memseek-search A 22 tokens
- Hook UserPromptSubmit A not measured
- Hook PreCompact A not measured
- Hook SessionStart A not measured
- Hook Stop A not measured
- Hook SessionEnd A not measured
- MCP server memseek A not measured
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 · 40 lines scan A 7c184e6567ad
memseek-memory is a plugin published in the GitHub repository memseekai/memseek (11 stars, last pushed 17d 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
atomicmemory
Persistent semantic memory for Claude Code — user preferences, project context, prior decisions, and codebase facts that survive across sessions.
ownmem
Git-native project memory for AI coding agents, with deterministic local recall, evidence gates, and layered delivery that quotes, points, or abstains.
perenna
A lightweight, Git-backed permanent memory for AI agents.
halomem
HaloMem organizational memory: session-start recall, session-end capture, MCP tools. Configure with HALOMEMURL and HALOMEMAPIKEY.
commitlore
Recorded decisions from git history, delivered to the agent before it edits. Constraints, alternatives already ruled out, and warnings left by whoever was here last.
goodmem
GoodMem memory infrastructure for AI agents. Use Python SDK skills to write code that manages embedders, spaces, and memories, or use MCP tools to perform GoodMem operations directly via natural language.