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/yonro/memory-os-cliWrote 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/yonro/memory-os-cli/xmemo)<a href="https://agentmods.dev/plugins/yonro/memory-os-cli/xmemo"><img src="https://agentmods.dev/badge/plugins/yonro/memory-os-cli/xmemo/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/yonro/memory-os-cli/xmemo"><img src="https://agentmods.dev/badge/plugins/yonro/memory-os-cli/xmemo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
xmemo 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 4d 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": "xmemo",
"displayName": "XMemo",
"version": "0.1.0",
"description": "Connect Cursor to XMemo's hosted, user-owned memory layer for durable project context, coding preferences, decisions, and reusable agent knowledge.",
"author": {
"name": "XMemo",
"email": "[email protected]"
},
"publisher": "XMemo",
"homepage": "https://xmemo.dev",
"repository": "https://github.com/yonro/memory-os-cli",
"license": "UNLICENSED",
"logo": "assets/logo.png",
"keywords": [
"cursor",
"plugin",
"mcp",
"memory",
"agent-memory",
"developer-tools",
"oauth"
],
"category": "Developer Tools",
"tags": [
"mcp",
"memory",
"oauth",
"developer-tools"
],
"rules": [
"rules/AGENTS.mdc"
],
"skills": [
"skills/agents/SKILL.md"
],
"mcpServers": "mcp.json"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 28 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.
- 4d ago First seen · 39 lines scan A b2bc42074fa8
xmemo is a plugin published in the GitHub repository yonro/memory-os-cli (12 stars, last pushed 2d 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-09-09.
Other plugins, from other repositories
stickies
A persistent sticky-note layer for Claude Code. Claude writes durable facts (decisions, blockers, preferences, context, todos) during a session; they survive resets and are injected back into context on the next start.
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).
mengram marketplace
Plugin marketplace listing 1 plugin: mengram.
mengram
Persistent memory for Claude Code that survives /clear, machine switches, and team handoffs. Hosted memory backend with hybrid retrieval, temporal decay, and cross-device sync.
prism-coder
Your coding agent forgets everything between sessions. Prism gives it a memory that sticks: your decisions, open TODOs, and changed files, restored the moment you return. It goes past a notes store — associative recall surfaces related past work, drift detection catches a long session wandering off-goal, and an…
cortex-plugins marketplace
Plugin marketplace listing 5 plugins: hypermnesia-mcp, cortex, hypermnesia-mcp-viz, cortex-viz, zetetic-team-subagents.