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 skills add yonro/memory-os-cli --skill xmemogit 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/skills/yonro/memory-os-cli/xmemo)<a href="https://agentmods.dev/skills/yonro/memory-os-cli/xmemo"><img src="https://agentmods.dev/badge/skills/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/skills/yonro/memory-os-cli/xmemo"><img src="https://agentmods.dev/badge/skills/yonro/memory-os-cli/xmemo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 118 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What 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.1 | $0.00068 | $0.04099 |
| Opus 5.5 | $0.00027 | $0.01640 |
| Sonnet 5.5 | $0.00014 | $0.00820 |
| Haiku 4.5 | $0.00007 | $0.00410 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 269 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, follow First-run sign-in below:
First-run sign-in (keep it short)
When no credential exists, follow this exact sequence:
- Ask once in the user's language using this canonical first-message template (translate when addressing the user in another language, but keep the template in English): "XMemo is your personal cloud memory — it lets AI remember your projects, preferences, and todos across sessions and tools, so you never have to repeat yourself. Using XMemo requires an account; you can create a new account or sign in to an existing one in your browser. Sign in or create an account to get started?" Show only this simple introduction and login question first, without doctor, MCP, token, commands, diagnostics, or technical setup.
- On yes: run
node scripts/xmemo-skill.mjs login --allow-plaintextdirectly so output is visible while the command is waiting (for example a background task or streaming shell). As soon as the verification URL and one-time code appear, show only those plus "approve it in your browser" — nothing else. Then wait for the command to exit. A short tool timeout must not kill it before approval or expiry. - When login succeeds: run
node scripts/xmemo-skill.mjs auth status --verify, tell the user in one line that XMemo is connected, and continue the original task. Silently runnode scripts/xmemo-skill.mjs profile --status later --if-unsetwith no user prompt, so the existing recall re-offer turns on. - On no: do not start login or create temporary access; continue the original task without XMemo; do not ask again in the same session unless the user brings it up.
- Do not explain runtime selection, doctor details, secret-store setup, or other features during sign-in unless the user asks.
Diagnostics and Advanced Setup
For troubleshooting or non-interactive environments:
- Check public service reachability:
node scripts/xmemo-skill.mjs doctor --anonymous - For account-backed memory, prefer an
XMEMO_KEYsupplied by a managed secret store (see references/auth-setup.md). - Inspect or verify credentials:
node scripts/xmemo-skill.mjs auth status --verify
What ships with it
28 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.
- CHANGELOG.md 28 KB
- references/agent-profile.md 5.2 KB
- references/auth-setup.md 9.3 KB
- references/command-details.md 7.8 KB
- references/ledger-operations.md 7.0 KB
- references/memory-operations.md 12 KB
- references/runtime-operations.md 8.7 KB
- references/troubleshooting.md 8.5 KB
- scripts/commands/account.mjs 7.5 KB runs code
- scripts/commands/auth-login.mjs 12 KB runs code
- scripts/commands/auth-manage.mjs 8.3 KB runs code
- scripts/commands/ledger.mjs 7.0 KB runs code
- scripts/commands/memory.mjs 12 KB runs code
- scripts/commands/ops.mjs 10 KB runs code
- scripts/commands/profile.mjs 1.8 KB runs code
- scripts/lib/api.mjs 12 KB runs code
- scripts/lib/auth-hint.mjs 716 B runs code
- scripts/lib/auth-state.mjs 11 KB runs code
- scripts/lib/bounded-read.mjs 5.1 KB runs code
- scripts/lib/cli-input.mjs 9.4 KB runs code
- scripts/lib/core.mjs 9.3 KB runs code
- scripts/lib/document-stub.mjs 4.0 KB runs code
- scripts/lib/error-text.mjs 3.2 KB runs code
- scripts/lib/help.mjs 8.2 KB runs code
- scripts/lib/muse-vault.mjs 6.4 KB runs code
- scripts/lib/openclaw-egress.mjs 3.0 KB runs code
- scripts/lib/profile-offer.mjs 3.6 KB runs code
- scripts/xmemo-skill.mjs 5.6 KB runs code
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 Changed · +7 lines 96193a23470d
- 13d ago Changed b0745c0b8b1e
- 14d ago Changed · -6 lines 1ab0c7136c1d
- 16d ago Changed befcfdab3680
- 18d ago Changed · +6 lines 07aad30bb0a7
- 19d ago Changed c9609c1cc09b
- 20d ago Changed · -220 lines · +16 tokens per session scan C → A 399dbb0f6523
- 21d ago Changed · +37 lines ee87dc7d071a
- 22d ago Changed · +9 tokens per session scan A → C a76bfc7b537e
- 23d ago First seen · 445 lines · 43 tokens per session scan A e49f0d6044c5
xmemo-memory is a skill published in the GitHub repository yonro/memory-os-cli (12 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 4,099 once invoked, about $0.0003 per session on Opus 5.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
perenna-memory
Use Perenna when a non-trivial task may depend on prior decisions or preferences, when durable knowledge should survive the session, or when the user asks to remember, forget, or consolidate memories. Skip self-contained tasks and facts already authoritative in the current workspace.
membrain
Shared long-term memory over MCP. Call memorycontext once at the start of any session/task to load what is already known; use searchmemory before answering questions about the user or their projects; save durable facts, preferences, and decisions with savememory / savememories. All agents and the user share the same…
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…
lesson
Store a lesson learned from the current conversation. Triggered by /lesson command. Use when Master signals that the recent conversation contains a pitfall, fix, or key insight that should be persisted to long-term memory.
recall
Recall this repository's OwnMem local memory before changing code, and keep it healthy. Use when a repository contains .ownmem/, when past debugging lessons could apply ("have we hit this before", "why is it done this way"), or when the user mentions ownmem, project memory, or recalling across sessions.
Effective Memory
The essential habits for an AI agent with memory — session bookends, learning triggers, verification, safety, and the operational discipline that turns raw recall into compounding intelligence. Keyword-matched after installation.