Custom Mode Creator for claude-mem
thedotmack/claude-mem
Walks you through creating, installing and verifying a custom claude-mem mode, including note types, tags and optional Telegram alerts for chosen memories.
Routes setup, troubleshooting and uninstall flows for mem9, a persistent cloud memory plugin for OpenClaw, and defines strict rules for config keys and API key handling.
$ npx skills add mem9-ai/mem9 --skill mem9 -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mem9-ai/mem9 mem9 --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mem9-ai/mem9.git skills-src && mkdir -p .claude/skills && cp -r skills-src/site/public .claude/skills/mem9 && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mem9" agent skill from https://github.com/mem9-ai/mem9/tree/main/site/public into .claude/skills/mem9/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem9", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mem9-ai/mem9/tree/main/site/publicType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mem9-ai/mem9 --skill mem9 -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mem9-ai/mem9 mem9 --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mem9-ai/mem9.git skills-src && mkdir -p .agents/skills && cp -r skills-src/site/public .agents/skills/mem9 && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mem9" agent skill from https://github.com/mem9-ai/mem9/tree/main/site/public into .agents/skills/mem9/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem9", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mem9-ai/mem9 --skill mem9 -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mem9-ai/mem9 mem9 --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mem9-ai/mem9.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/site/public .cursor/skills/mem9 && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mem9" agent skill from https://github.com/mem9-ai/mem9/tree/main/site/public into .cursor/skills/mem9/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem9", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mem9-ai/mem9.git --path site/public--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mem9-ai/mem9 --skill mem9 -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mem9-ai/mem9 mem9 --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mem9-ai/mem9.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/site/public .gemini/skills/mem9 && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mem9" agent skill from https://github.com/mem9-ai/mem9/tree/main/site/public into .gemini/skills/mem9/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem9", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mem9-ai/mem9 mem9Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mem9-ai/mem9 --skill mem9 -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mem9-ai/mem9.git skills-src && mkdir -p .github/skills && cp -r skills-src/site/public .github/skills/mem9 && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mem9" agent skill from https://github.com/mem9-ai/mem9/tree/main/site/public into .github/skills/mem9/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem9", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mem9-ai/mem9 --skill mem9 -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mem9-ai/mem9 mem9 --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mem9-ai/mem9.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/site/public .opencode/skills/mem9 && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mem9" agent skill from https://github.com/mem9-ai/mem9/tree/main/site/public into .opencode/skills/mem9/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem9", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
mem9Routes setup, troubleshooting and uninstall flows for mem9, a persistent cloud memory plugin for OpenClaw, and defines strict rules for config keys and API key handling.
This top-level document routes first-time install, reconnect, config review and mainland China or Alibaba Cloud npm handling to SETUP.md, setup failures and broken local state to TROUBLESHOOTING.md, and local removal to UNINSTALL.md. It is a routing and safety document, not the canonical reference for runtime request behavior.
Install rules are strict: mem9 is installed only through openclaw plugins install, never a global npm install, because OpenClaw does not discover global packages as plugins. Only plugins.entries.mem9.config.apiKey is a valid config key, never plugins.entries.mem9.apiKey, and OpenClaw 4.23 or later needs plugins.entries.mem9.hooks.allowConversationAccess set to true so mem9 can read conversation messages during agent_end.
Setup verification stays deterministic: if the first post-restart message produces no key, the one local OpenClaw agent trigger from SETUP.md runs in that same turn instead of asking for repeated test messages. A missing API key during create-new mode is not treated as failure until the generated key is verified. API keys are kept out of local memory and history notes during setup and shown only in the final onboarding handoff message, and history import from local session files stays manual.
Read from SKILL.md and the folder at commit 071a4e8. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npmFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
api.mem9.aiAlso links to:
mem9.aiFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
mem9 Memory Plugin Setup loads about 1.4k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 635 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mem9-ai/mem9 at commit 071a4e8, republished under its Apache-2.0 licence (© mem9-ai). 635 words, ~1,381 tokens.
.claude/skills/mem9/SKILL.md (or your agent's skills folder). This skill also uses 19 other files; get the full folder from GitHub.mem9 is the persistent cloud memory plugin for OpenClaw. It keeps durable memory across sessions and machines.
This top-level SKILL.md is a routing and safety document. It is the entry point for setup, troubleshooting, and uninstall flows. It is not the canonical reference for runtime request behavior.
SETUP.md.TROUBLESHOOTING.md.UNINSTALL.md.utm_* params from a remote SKILL.md URL through the create-new setup flow and first restart.openclaw plugins install @mem9/mem9; never substitute npm install -g @mem9/mem9, because OpenClaw does not discover global npm packages as plugins.plugins.entries.mem9.apiKey; only plugins.entries.mem9.config.apiKey is valid.plugins.entries.mem9.hooks.allowConversationAccess = true so mem9 can read conversation messages during agent_end.SETUP.md in that same resumed turn; never ask for repeated hi messages.plugins.entries.mem9.config.apiKey as failure. The generated key is verified from mem9 logs or local provision state until the user explicitly reconnects with it.✅ Your mem9 API key is connected. followed by 🧭 WHAT YOU CAN DO NEXT; never replace it with a brief success summary.MEMORY.md, memory/*.md, or equivalent local logs; show the key only in the final onboarding handoff.https://api.mem9.ai unless the user explicitly chooses another apiUrl.SKILL.md is not the backend API contract and does not define day-to-day memory semantics.Only these openclaw.json paths may be changed during setup:
plugins.slots.memoryplugins.entries.mem9.enabledplugins.entries.mem9.hooks.allowConversationAccess for OpenClaw 4.23+ / 2026.4.22+ onlyplugins.entries.mem9.config.apiUrlplugins.entries.mem9.config.apiKeyplugins.entries.mem9.config.provisionToken for create-new only; generate it once per create-new run before the first restart and keep it stable through the first successful post-restart provision on this machineplugins.entries.mem9.config.provisionQueryParams for create-new only, and only when the remote SKILL.md URL contains filtered utm_* parameters; when present, it must be written before the first restartplugins.allowDo not change any other config keys unless the user explicitly asks.
The scope above is exhaustive. In particular, do not write plugins.entries.mem9.apiKey at the entry top level. OpenClaw rejects that key as invalid config before the mem9 plugin can load.
SETUP.md.TROUBLESHOOTING.md.UNINSTALL.md.reset session, restart gateway, 重启网关, clearing local mem9 history, or equivalent, still route to UNINSTALL.md first and keep those actions as post-verification follow-up only.SETUP.md, TROUBLESHOOTING.md, and UNINSTALL.md relative to the directory containing the current SKILL.md.SETUP.md, TROUBLESHOOTING.md, or UNINSTALL.md.openclaw.json paths outside the allowed scope were changed.© mem9-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 19 other files in site/public of mem9-ai/mem9.
Open the folder on GitHubat commit 071a4e8
mem9 Memory Plugin Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| mem9 Memory Plugin Setup this skillmem9-ai/mem9 | 1.2k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Custom Mode Creator for claude-memthedotmack/claude-mem | 99k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Beads Task Memorygastownhall/beads | 28k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Reflect on Session Learningscursor/plugins | 10k | 5 repos | ~1.2k | Automated safety check: Pass | None | |
| MemPalace Memory SearchMemPalace/mempalace | 59k | — | ~1.4k | Automated safety check: Pass | MIT |
thedotmack/claude-mem
Walks you through creating, installing and verifying a custom claude-mem mode, including note types, tags and optional Telegram alerts for chosen memories.
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
gastownhall/beads
Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.
cursor/plugins
Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.
MemPalace/mempalace
Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.
EveryInc/compound-engineering-plugin
Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.
mem9-ai/mem9
Deploys a mnemo-server instance, provisions a tenant, and wires persistent memory into OpenClaw, OpenCode or Claude Code.
Categories
Routes setup, troubleshooting and uninstall flows for mem9, a persistent cloud memory plugin for OpenClaw, and defines strict rules for config keys and API key handling. md. It is a routing and safety document, not the canonical reference for runtime request behavior.
mem9 Memory Plugin Setup fits situations like: installing the mem9 memory plugin for OpenClaw for the first time; troubleshooting a broken or incomplete mem9 setup; uninstalling mem9 from a local machine; checking which config keys are valid for the mem9 plugin.
Run `npx skills add mem9-ai/mem9 --skill mem9 -a claude-code`. Or copy the skill folder (site/public in mem9-ai/mem9) into .claude/skills/mem9 in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mem9-ai/mem9 --skill mem9 -a codex`. Or copy the skill folder (site/public in mem9-ai/mem9) into .agents/skills/mem9 in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mem9-ai/mem9 --skill mem9 -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mem9, .gemini/skills/mem9, .github/skills/mem9 and .opencode/skills/mem9 in your project.
Going by SKILL.md and its folder, mem9 Memory Plugin Setup needs the command-line tools its instructions call (npm). Our summary lists: OpenClaw, version 4.23 or later for conversation-access hooks.
SKILL.md names 2 domains. In commands or code: api.mem9.ai; the agent is likely to contact it when it follows the instructions. As links in the text: mem9.ai. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
mem9 Memory Plugin Setup is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with mem9 Memory Plugin Setup: Custom Mode Creator for claude-mem (thedotmack/claude-mem, 99k stars), Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Beads Task Memory (gastownhall/beads, 28k stars) and Reflect on Session Learnings (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mem9-ai (a GitHub organization) maintains it in mem9-ai/mem9, which has 1,223 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 29, 2026.
Source: mem9-ai/mem9 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.