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/plur-ai/plur/clawhubnpx skills add plur-ai/plur --skill clawhubgit clone --depth 1 https://github.com/plur-ai/plurWhat 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 | $0.00041 | $0.00531 |
| Opus 5 | $0.00020 | $0.00266 |
| Sonnet 5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
plur-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 yesterday.
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
PLUR Memory
Most memory plugins send your context to a cloud server. PLUR doesn't.
Your memory lives on your disk — plain files you can read, edit, move, and back up. Zero cloud routing. Zero API keys. Zero cost.
Install in one command:
openclaw plugins install @plur-ai/claw
Or tell your OpenClaw: go to plur.ai and install memory
What happens next
Every correction you make becomes a permanent engram. Every preference gets remembered. The next time you open a session, PLUR injects what's relevant — automatically, before you type a word.
One memory, every tool
Correct something in OpenClaw — your Claude Code picks it up. Teach a pattern in Cursor — OpenClaw already knows. Memory moves with you across every MCP-compatible tool you use.
Features
- Learns from corrections and preferences as you work — no manual notes
- Injects relevant context at session start — no re-explaining from scratch
- Memory strengthens with use, fades when stale — modeled on human memory
- Works across Claude Code, Cursor (beta), and any MCP-compatible tool
- No cloud, no API key, no cost — by default
Benchmarks
- Retrieval (LongMemEval R@5): 76.7% out-of-the-box · 97.0% with openai-3-large embeddings — full methodology
- Agent tasks: 89% win rate — Haiku + PLUR outperforms Opus without memory
- House rules: 12–0 across Haiku, Sonnet, Opus
Open source. Local-first. Private. Free.
Apache-2.0. Your data never leaves your machine.
Requirements
- OpenClaw >= 2026.3.7
- Node.js >= 18
Links
- Website: https://plur.ai
- GitHub: https://github.com/plur-ai/plur
- npm: https://npmjs.com/package/@plur-ai/claw
- Benchmarks: https://plur.ai/benchmark.html
Author: PLUR ([email protected])
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.
- yesterday First seen · 60 lines · 41 tokens per session scan A e68ae13c2cda
plur-memory is a skill published in the GitHub repository plur-ai/plur (243 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 531 once invoked, about $0.0002 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
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…
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.
mnemo-cortex
Installs and wires Mnemo Cortex (local-first persistent memory) into OpenClaw and other MCP-capable agents. Use for cross-session recall, decision history, or multi-agent shared memory.
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.
ogham-research
Structured memory capture for Ogham shared memory. Use when the user wants to store findings, remember something, save what was learned, or capture a decision. Triggers on "remember this", "store this", "save this finding", "save what we learned", "capture this decision", "log this", or any request to persist…
add-memory-system
Research and integrate a new agent-memory repository into Agent Memory Atlas. Use when asked to add, analyze, catalog, or compare a memory system in this repository, including its commit-pinned system report, comparative overview coverage, homepage card, generated site, and validation.