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 skills add TheophilusChinomona/claude-openclaw-plugin --skill openclaw-memory-curatorgit clone --depth 1 https://github.com/TheophilusChinomona/claude-openclaw-pluginWrote 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/theophiluschinomona/claude-openclaw-plugin/openclaw-memory-curator)<a href="https://agentmods.dev/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-memory-curator"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-memory-curator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-memory-curator"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-memory-curator.svg" alt="Reviewed on agentmods" width="80" 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.00150 | $0.01419 |
| Opus 5 | $0.00075 | $0.00709 |
| Sonnet 5 | $0.00030 | $0.00284 |
| Haiku 4.5 | $0.00015 | $0.00142 |
Grade A, and why
openclaw-memory-curator 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenClaw Memory Curator
Audit, clean, and curate agent memory — keeping MEMORY.md accurate, relevant, and lean as the business evolves.
Why Memory Degrades
Agent memory goes stale in predictable ways:
- Completed goals stay in Active — nothing moves them to Completed
- Old client data persists — invoices that were paid still show "outstanding"
- Daily logs accumulate — valuable facts buried in chronological noise
- Contradictions build up — the agent was told X, then later told Y, both remain
- Lessons get forgotten — buried in daily logs, never promoted to MEMORY.md
This skill fixes all of it systematically.
Stage 1: Memory Audit
For the agent(s) being curated, request or read:
MEMORY.md(if it exists)- Recent
memory/YYYY-MM-DD.mddaily logs (last 30-90 days) GOALS.md
If files are on the server, user provides them as uploads or pastes.
Audit checklist:
MEMORY AUDIT — [Agent Name] — [Date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MEMORY.md:
□ Last updated date: [date]
□ Stale client entries: [list any clients with outdated status]
□ Stale invoice entries: [outstanding invoices older than 60 days]
□ Outdated contact details: [any contacts marked [TBC] or [confirm]]
□ Contradictions found: [any section where two facts conflict]
□ Sections that need adding: [what's missing that should be there]
DAILY LOGS:
□ Days reviewed: [n days]
□ Durable facts found: [facts worth promoting to MEMORY.md]
□ Completed goals found: [goals referenced as done but still in Active]
□ New lessons found: [lessons that should go to Lessons Learned]
GOALS.md:
□ Goals marked complete in conversation but still in Active
□ Goals with status "Not started" for 60+ days — still relevant?
□ Missing goals from recent work
□ Milestones table accurate?
Stage 2: Extract Durable Facts from Daily Logs
Read daily logs and extract facts worth keeping in MEMORY.md:
Promote to MEMORY.md when:
- A new client relationship was established
- An invoice was paid or a financial decision was made
- A process lesson was learned from experience
- A contact's details or role changed
- A service was added, changed, or removed
- A preference was stated by Tino or a client
- A goal was completed
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.
- 11d ago First seen · 178 lines · 150 tokens per session scan A 6097ca9bde7e
openclaw-memory-curator is a skill published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 150 tokens to every session and 1,419 once invoked, about $0.0007 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.