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.
/plugin marketplace add lopadova/claude-mem-syncnpx agentmods add plugins/lopadova/claude-mem-sync/marketplacegit clone --depth 1 https://github.com/lopadova/claude-mem-syncWrote 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/lopadova/claude-mem-sync/marketplace)<a href="https://agentmods.dev/plugins/lopadova/claude-mem-sync/marketplace"><img src="https://agentmods.dev/badge/plugins/lopadova/claude-mem-sync/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
claude-mem-sync marketplace 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 6d 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": "claude-mem-sync",
"owner": {
"name": "lopadova"
},
"metadata": {
"description": "Team memory sharing plugins for claude-mem"
},
"plugins": [
{
"name": "claude-mem-sync",
"source": {
"source": "github",
"repo": "lopadova/claude-mem-sync"
},
"description": "Team memory sharing for claude-mem — tracks observation access for intelligent eviction scoring",
"version": "1.1.9"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.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.
- 6d ago First seen · 21 lines scan A 59acee5a298e
claude-mem-sync marketplace is a plugin published in the GitHub repository lopadova/claude-mem-sync (25 stars, last pushed 2mo ago), 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
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.
hivemind marketplace
Plugin marketplace listing 1 plugin: hivemind.
hivemind
Cloud-backed persistent memory powered by Deeplake — read, write, and share memory across Claude Code sessions and agents.
claude-mem
Memory compression system for Claude Code - persist context across sessions.
celiums
Persistent memory for Claude Code through the authenticated native Rust server. 5 hooks + 6 MCP tools + 9 cognitive reflex skills.