Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/parallelclaw/memex-mvp/install-memex-claw)<a href="https://agentmods.dev/skills/parallelclaw/memex-mvp/install-memex-claw"><img src="https://agentmods.dev/badge/skills/parallelclaw/memex-mvp/install-memex-claw.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.00297 | $0.05198 |
| Opus 5 | $0.00148 | $0.02599 |
| Sonnet 5 | $0.00059 | $0.01040 |
| Haiku 4.5 | $0.00030 | $0.00520 |
Grade C, and why
install-memex-claw scanned grade C with 2 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 8d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
- ❌ Install Node.js (manual step if needed — print instructions, don't auto-install) Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| `loginctl enable-linger $USER` (Linux only) | Without linger, user-systemd dies on SSH logout — daemon would stop between SSH sessions on a VPS. Skill tries this; if sudo needed, prints command and continues. | Standar How it starts
The opening of the file, as written. The whole thing — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install memex for OpenClaw
You are inside an OpenClaw agent. The user asked you to set up memex — the local-first MCP memory server — so that:
- Every OpenClaw session in
~/.openclaw/agents/main/sessions/is auto-captured into~/.memex/data/memex.db(SQLite + FTS5). - Existing past sessions are back-filled in one shot.
- The OpenClaw gateway gains the
memexMCP server with 11 search/retrieval tools (memex_search, memex_recent, memex_overview, memex_get_conversation, etc.). - Capture continues automatically thereafter (systemd user-service on Linux, LaunchAgent on macOS).
Where you might be running:
- 🖥️ VPS (Linux VPS hosting OpenClaw + maybe Hermes) — typical "always-on agent" deployment
- 💻 macOS workstation running OpenClaw alongside Claude Code / etc.
- 💻 Linux workstation (Pop!OS, Fedora, etc.) running OpenClaw locally
- 🤖 Moonshot Kimi-Claw VPS — also works (memex-mvp ≥ 0.11.5 auto-detects the merged-file Kimi-Claw layout)
All work the same way. Platform (Linux/macOS) determines daemon type. Deployment kind (self-hosted vs Kimi-Claw vs workstation) is auto-detected by the memex-mvp daemon.
The contract: zero questions to the user. Discovery → actions → verification. Each step prints a single line of result. The final message tells the user exactly what to do next.
⚠ For ClawHub reviewers, security scanners, and curious users
This skill installs memex-mvp from npm (if not already present) and wires it as an MCP server inside the OpenClaw gateway config. memex-mvp's memex-sync daemon auto-captures every OpenClaw session at the file-watcher layer — works on every OpenClaw deployment (self-hosted + Moonshot Kimi-Claw + workstations), no plugin-SDK involvement.
| Action | Why | Source |
|---|---|---|
npm install -g memex-mvp@latest |
Install the MCP server + the auto-capture daemon. Open-source MIT. Skipped if already installed. | npmjs.com/package/memex-mvp, source: github.com/parallelclaw/memex-mvp |
memex-sync install |
Register the auto-capture daemon — systemd user-service on Linux, LaunchAgent on macOS. The daemon watches ~/.openclaw/agents/main/sessions/ and writes to ~/.memex/data/memex.db. Zero outbound network traffic. Skipped if daemon already running. |
LaunchAgent at ~/Library/LaunchAgents/com.parallelclaw.memex.sync.plist or systemd unit at ~/.config/systemd/user/memex-sync.service — both human-readable |
loginctl enable-linger $USER (Linux only) |
Without linger, user-systemd dies on SSH logout — daemon would stop between SSH sessions on a VPS. Skill tries this; if sudo needed, prints command and continues. | Standard systemd-user practice |
Edit OpenClaw config at ~/.openclaw/openclaw.json |
Add a single memex entry under mcp.servers. Merge, never overwrite other entries. |
The OpenClaw gateway reads this file at startup |
memex-sync scan |
One-shot back-fill of past OpenClaw sessions. Walks the sessions dir, parses each <uuid>.jsonl, writes to memex.db with source='openclaw'. Filters internal-state noise files (.checkpoint., .trajectory., .reset.). |
lib/ingest-file.js in the source — open-source |
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.
- 8d ago First seen · 424 lines · 297 tokens per session scan C eac5917b3da5
install-memex-claw is a skill published in the GitHub repository parallelclaw/memex-mvp (13 stars, last pushed 2mo ago), licensed MIT. It adds 297 tokens to every session and 5,198 once invoked, about $0.0015 per session on Opus 5. A static security scan graded it C with 2 findings (asks the agent to reveal its instructions, asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
dashboard
Open OwnMem Console, the local dashboard for this repository's memory. Use when the user asks to open the dashboard, see memory metrics, check adoption or recall quality, or set up the optional embedding lane. Requires a repository initialized with the dashboard layer.
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.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
memorize
Curates insights from reflections and critiques into CLAUDE.md using Agentic Context Engineering.
everme-memory
Use EverMe cloud memory proactively when the user refers to previous conversations, earlier decisions, "last time", "remember when", existing project conventions, or previously solved errors, and save durable user preferences, habits, and decisions the moment they are stated. Do not repeat a search when the host…
memory-tools
Use EverMe memory proactively when the user refers to previous conversations, earlier decisions, "last time", "remember when", existing project conventions, or previously solved errors, and save durable user preferences, habits, and decisions the moment they are stated. Do not repeat a search when a non-empty block…