Coding Agent Session Finder
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
Deploys a mnemo-server instance, provisions a tenant, and wires persistent memory into OpenClaw, OpenCode or Claude Code.
$ npx skills add mem9-ai/mem9 --skill mnemos-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mem9-ai/mem9 mnemos-setup --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/skills/mnemos-setup .claude/skills/mnemos-setup && 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 "mnemos-setup" agent skill from https://github.com/mem9-ai/mem9/tree/main/skills/mnemos-setup into .claude/skills/mnemos-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mnemos-setup", 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/skills/mnemos-setupType 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 mnemos-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mem9-ai/mem9 mnemos-setup --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/skills/mnemos-setup .agents/skills/mnemos-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mnemos-setup" agent skill from https://github.com/mem9-ai/mem9/tree/main/skills/mnemos-setup into .agents/skills/mnemos-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mnemos-setup", 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 mnemos-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mem9-ai/mem9 mnemos-setup --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/skills/mnemos-setup .cursor/skills/mnemos-setup && 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 "mnemos-setup" agent skill from https://github.com/mem9-ai/mem9/tree/main/skills/mnemos-setup into .cursor/skills/mnemos-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mnemos-setup", 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 skills/mnemos-setup--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 mnemos-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mem9-ai/mem9 mnemos-setup --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/skills/mnemos-setup .gemini/skills/mnemos-setup && 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 "mnemos-setup" agent skill from https://github.com/mem9-ai/mem9/tree/main/skills/mnemos-setup into .gemini/skills/mnemos-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mnemos-setup", 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 mnemos-setupInstalls 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 mnemos-setup -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/skills/mnemos-setup .github/skills/mnemos-setup && 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 "mnemos-setup" agent skill from https://github.com/mem9-ai/mem9/tree/main/skills/mnemos-setup into .github/skills/mnemos-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mnemos-setup", 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 mnemos-setup -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 mnemos-setup --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/skills/mnemos-setup .opencode/skills/mnemos-setup && 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 "mnemos-setup" agent skill from https://github.com/mem9-ai/mem9/tree/main/skills/mnemos-setup into .opencode/skills/mnemos-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mnemos-setup", 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.
mnemos-setupDeploys a mnemo-server instance, provisions a tenant, and wires persistent memory into OpenClaw, OpenCode or Claude Code.
This skill sets up mnemos, a persistent memory server, end to end: running the Go-based mnemo-server against a configured database connection string, then provisioning a tenant through an API call that returns a tenant id to save - stored as an apiKey value in newer configs, or as the equivalent legacy tenantID field.
From there it configures whichever agent platform is in use. OpenClaw gets a memory plugin entry in its config file, plus on newer builds an explicit hook permission so the plugin can read and upload conversation messages. OpenCode gets environment variables plus a plugin entry in its own config. Claude Code gets environment variables in its settings file plus a marketplace plugin install.
After setup it has you verify that memory is actually working end to end, and restart the chosen platform so the newly added plugin or environment variables actually take effect before relying on it.
3 steps, taken from the step headings in SKILL.md.
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:
gocurljqFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From 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.
Mnemos Memory Setup loads about 895 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 292 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 noted patterns worth knowing about, such as sudo or a known installer.
ment variables (add to shell profile or `.env`):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). 292 words, ~895 tokens.
.claude/skills/mnemos-setup/SKILL.md (or your agent's skills folder).Persistent memory for AI agents. This skill helps you set up mnemos with any agent platform.
You need a running mnemo-server instance. See the server README for deployment instructions.
cd mnemos/server
MNEMO_DSN="user:pass@tcp(host:4000)/mnemos?parseTime=true" go run ./cmd/mnemo-servercurl -s -X POST http://localhost:8080/v1alpha1/mem9s | jq .
# → { "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "claim_url": "..." }Save the returned id.
apiKey (preferred).tenantID, but the plugin will still use v1alpha2.Pick your platform and follow the instructions:
Add to openclaw.json:
{
"plugins": {
"slots": { "memory": "mem9" },
"entries": {
"mem9": {
"enabled": true,
"hooks": {
"allowConversationAccess": true
},
"config": {
"apiUrl": "http://localhost:8080",
"apiKey": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}
}
}
}
}Restart OpenClaw. You should see:
[mem9] Server mode (v1alpha2)Compatibility note:
apiKey -> plugin uses v1alpha2 with X-API-Key.tenantID -> plugin treats it as an alias for apiKey and still uses v1alpha2.plugins.entries.mem9.hooks.allowConversationAccess = true so mem9 can read conversation messages in agent_end and upload them. Older OpenClaw builds that reject this hook policy should omit the hooks block and upgrade for full automatic conversation upload.Set environment variables (add to shell profile or .env):
export MNEMO_API_URL="http://localhost:8080"
export MNEMO_TENANT_ID="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"Add to opencode.json:
{
"plugin": ["mnemo-opencode"]
}Restart OpenCode. You should see:
[mem9] Server mode (mnemo-server REST API)Add to ~/.claude/settings.json:
{
"env": {
"MNEMO_API_URL": "http://localhost:8080",
"MNEMO_TENANT_ID": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}
}Install plugin:
/plugin marketplace add mem9-ai/mem9
/plugin install mnemo-memory@mnemosRestart Claude Code.
After setup, test memory:
The agent should recall the information from memory.
| Problem | Fix |
|---|---|
No MNEMO_API_URL configured | Set MNEMO_API_URL env var or apiUrl in plugin config |
MNEMO_TENANT_ID is not set | Set MNEMO_TENANT_ID for env-based clients, or use apiKey (preferred) / legacy tenantID in OpenClaw plugin config |
| Plugin not loading | Check platform-specific config format |
© 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
Just SKILL.md in skills/mnemos-setup of mem9-ai/mem9.
Open the folder on GitHubat commit 071a4e8
Mnemos Memory 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 |
|---|---|---|---|---|---|---|
| Mnemos Memory Setup this skillmem9-ai/mem9 | 1.2k | — | ~895 | Automated safety check: Notes | Apache-2.0 | |
| Coding Agent Session Findercode-yeongyu/oh-my-openagent | 70k | 1 repos | ~2.8k | Automated safety check: Pass | Custom licence | |
| Claude-Mem Cloud Syncthedotmack/claude-mem | 98k | 1 repos | ~1k | Automated safety check: Notes | Apache-2.0 | |
| Cognee CLI Memory Commandstopoteretes/cognee | 32k | 1 repos | ~2.2k | Automated safety check: Notes | Apache-2.0 | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Claude-Mem Searchthedotmack/claude-mem | 98k | 1 repos | ~511 | Automated safety check: Pass | Apache-2.0 |
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
thedotmack/claude-mem
Checks claude-mem cloud sync status and guides you through connecting a cmem.ai Pro account without the sync token ever passing through the chat.
topoteretes/cognee
Drives cognee from the terminal with remember, recall, forget and improve memory commands, dataset and config management and database migrations.
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.
thedotmack/claude-mem
Searches the user's persistent cross-session memory for timestamped observations synthesized from past agent sessions on cmem.ai.
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.
mem9-ai/mem9
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.
Categories
Deploys a mnemo-server instance, provisions a tenant, and wires persistent memory into OpenClaw, OpenCode or Claude Code. This skill sets up mnemos, a persistent memory server, end to end: running the Go-based mnemo-server against a configured database connection string, then provisioning a tenant through an API call that returns a tenant id to save - stored as an apiKey value in newer configs, or as the equivalent legacy tenantID field.
Mnemos Memory Setup fits situations like: setting up persistent memory for an OpenClaw, OpenCode or Claude Code agent; provisioning a new mnemos tenant and connecting it to an agent; troubleshooting why a configured memory plugin isn't reporting server mode.
Run `npx skills add mem9-ai/mem9 --skill mnemos-setup -a claude-code`. Or copy the skill folder (skills/mnemos-setup in mem9-ai/mem9) into .claude/skills/mnemos-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mem9-ai/mem9 --skill mnemos-setup -a codex`. Or copy the skill folder (skills/mnemos-setup in mem9-ai/mem9) into .agents/skills/mnemos-setup 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 mnemos-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mnemos-setup, .gemini/skills/mnemos-setup, .github/skills/mnemos-setup and .opencode/skills/mnemos-setup in your project.
Going by SKILL.md and its folder, Mnemos Memory Setup needs the command-line tools its instructions call (go, curl and jq). Our summary lists: A running mnemo-server instance; Go toolchain to run mnemo-server.
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Mnemos Memory 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 895 tokens (SKILL.md is roughly 3.6k 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 Mnemos Memory Setup: Coding Agent Session Finder (code-yeongyu/oh-my-openagent, 70k stars), Claude-Mem Cloud Sync (thedotmack/claude-mem, 98k stars), Cognee CLI Memory Commands (topoteretes/cognee, 32k stars) and Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k 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.