mem9 is a persistent memory service for AI agents that preserves information across sessions and machines and can share it among multiple agents. It is used with OpenClaw, coding agents, workflow platforms, and custom clients that need shared storage and recall. The catalogue add-ons connect agents and workflows to mem9 memory.
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/mem9-ai/mem9/cleanupnpx skills add mem9-ai/mem9 --skill cleanupgit clone --depth 1 https://github.com/mem9-ai/mem9Wrote 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/mem9-ai/mem9/cleanup)<a href="https://agentmods.dev/skills/mem9-ai/mem9/cleanup"><img src="https://agentmods.dev/badge/skills/mem9-ai/mem9/cleanup.svg" alt="Measured on agentmods" height="20"></a>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.00019 | $0.00375 |
| Opus 5 | $0.00010 | $0.00187 |
| Sonnet 5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
cleanup 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
Mem9 Cleanup
Resolve ./scripts/cleanup.mjs relative to this skill directory.
If you need the current CLI surface, flags, or examples, run node ./scripts/cleanup.mjs --help first.
Use command-specific help when needed, for example node ./scripts/cleanup.mjs run --help.
Run this workflow:
- Inspect the current cleanup targets first:
set -euo pipefail
node ./scripts/cleanup.mjs inspect
- Use the JSON summary to confirm whether cleanup should cover only global Codex files or the current project's local override too.
- Remove mem9-managed global Codex files with:
set -euo pipefail
node ./scripts/cleanup.mjs run
- When the current repository's local override should be removed too, run:
set -euo pipefail
node ./scripts/cleanup.mjs run --include-project
Common flags:
inspectrun--include-project--cwd <repo-root>
run removes mem9-managed entries from $CODEX_HOME/hooks.json, $CODEX_HOME/mem9/hooks/, $CODEX_HOME/mem9/install.json, $CODEX_HOME/mem9/config.json, and $CODEX_HOME/mem9/state.json.
run --include-project also removes <project>/.codex/mem9/config.json.
Keep $MEM9_HOME/.credentials.json, $CODEX_HOME/config.toml, and mem9 debug logs untouched.
Do not print API keys or credential file contents.
What ships with it
1 file 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.
- 6d ago First seen · 52 lines · 19 tokens per session scan A 34727a8fe343
cleanup is a skill published in the GitHub repository mem9-ai/mem9 (1,206 stars, last pushed 11d ago), licensed Apache-2.0. It adds 19 tokens to every session and 375 once invoked, about $0.0001 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
dsh-web-pre-push-checks
Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.
dsh-web-documentation
Use when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.
dsh-sdk-upgrade
Safely select and install a compatible official @deepseek-ai SDK release for dsh plugin projects (dsh-web, dsh-trading, and similar monorepos) from npm using an isolated worktree, explicit cohort review, CI-equivalent validation, and controlled rollout — including syncing the project's declared DSH host-version floor…
dsh-web-sdk-compatibility
Adapt and repair dsh-web after an approved official @deepseek-ai SDK/runtime cohort is selected or installed. Compare public API, type, service-injection, module-table, protocol, and behavior changes; map every change to repository consumers; implement the smallest fixes and durable compatibility contracts; handle…
ov-experience-memory
Retrieve and apply OpenViking Experience memories through the Agent runtime's generic OpenViking search and read tools. Use before or during executable, multi-step, or tool-based work such as coding, file or data changes, configuration, deployment, workflow execution, and failure recovery when prior operational…
task-planning-arch
计算任务 gap 并产出下一步可执行子任务 List[TaskSpec];gap 已闭返回空数组。对齐 arch 场景(架构师名册/技术栈概览/双视角分析)确定式分解——按根目标交付物集合 + donechildren 查表(参照 task-planning storage 特例,非自由 LLM 分解)。.