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.
npx agentmods add skills/yonro/memory-os-cli/xmemonpx skills add yonro/memory-os-cli --skill xmemogit clone --depth 1 https://github.com/yonro/memory-os-cliWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00043 | $0.02607 |
| Opus 5 | $0.00022 | $0.01303 |
| Sonnet 5 | $0.00009 | $0.00521 |
| Haiku 4.5 | $0.00004 | $0.00261 |
Grade A, and why
xmemo-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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XMemo Memory
Give your agent durable memory that survives across sessions, projects, and tools.
First Successful Run
After ClawHub installs this Skill, run these commands from the Skill root to confirm the service and choose an authentication path in a few minutes:
-
Check public service reachability without sending a credential:
node scripts/xmemo-skill.mjs doctor --anonymous -
For account-backed memory, prefer an
XMEMO_KEYsupplied by a managed secret store. Otherwise, start the formal device-login flow only when you explicitly accept local plaintext credential storage:node scripts/xmemo-skill.mjs login --allow-plaintext -
Confirm the credential before running memory operations:
node scripts/xmemo-skill.mjs auth status --verify
If a command fails, use the exact next action it prints, then read
references/troubleshooting.md. Once the check succeeds, continue with
Core Workflows below.
Runtime Selection
XMemo supports two parallel integration paths:
- Bundled Skill script at
scripts/xmemo-skill.mjs(primary standalone direct REST API integration, fully self-contained and zero-dependency). - XMemo MCP tools (when running in environments that natively host the XMemo MCP server).
Run bundled commands from the Skill root with Node.js 22.22.0 or newer. This matches the MemoryOS service and repository runtime baseline.
Hosted Discovery Boundary
The public agent-discovery field standalone_skill.operations describes the
generic commands accepted by POST /v1/skill/operations; it is not the full
standalone command catalogue. restart-snapshot and restart-restore use the
separate direct endpoints /v1/restart/snapshot and /v1/restart/restore, so
they are deliberately absent from that operations list.
Do not infer that a restart command is available merely because a discovery
document mentions a memory scope. It requires a formal account credential and
the service must authorize the specific request. The temporary-agent manifest
intentionally omits restart continuity: temporary access stays limited to
remember, recall, and search in its isolated sandbox.
What ships with it
4 files beside SKILL.md 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.
- 2d ago First seen · 250 lines · 43 tokens per session scan A 7b7e289ed2c7
xmemo-memory is a skill published in the GitHub repository yonro/memory-os-cli (12 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 2,607 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
weasley-deepmind
AI 에이전트가 weasley-deepmind 기억 서버를 최대 효율로 활용하기 위한 기술 레퍼런스.
mnema
Use the Mnema MCP server to give the AI long-term, searchable memory. Use it whenever the user shares durable facts, preferences, decisions, or context worth recalling in future sessions. Mnema stores memories in a vector database and recalls them with semantic + hybrid search, with decay scoring and summarization so…
stickies
Capture and recall persistent sticky notes — decisions, blockers, todos, preferences, and context — that survive across Claude sessions, kept in a local SQLite store (no account, no API key). Use this skill whenever the user wants to remember something for later, jot a note, park a todo or follow-up, record a decision…
graphmind-planning
Декомпозиция сложной задачи в иерархию планов GraphMind по MCP. Создать P0-проблему (plancreatep0), предложить P1-подпланы для ревью (planproposep1/approvep1/rejectp1), декомпозировать в P2/P3, выдать P3 суб-агенту (planclaim), завершить с результатом (plancomplete). Использовать, когда задача большая, размытая или…
graphmind-memory
Работа с постоянной памятью GraphMind по MCP. Восстановить контекст проекта в начале работы (bootstrapmemory), сохранять шаги и решения по ходу (recordaction, proposenewmemory), консолидировать и сохранить в конце (flushsessionmemory). Использовать, когда нужна память между сессиями, семантический поиск по…
using-cortex-memory
Use when connected to a Cortex memory MCP server (tools named memorize, recall, recallabout, recalltimeline, listmemories, forget) — at session start, before asking the user for facts they may have shared before, after learning durable facts/preferences/decisions, when the user says "remember/recall/forget", or when…