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/webrenew/memories/openclawnpx skills add webrenew/memories --skill openclawgit clone --depth 1 https://github.com/webrenew/memoriesWrote 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/webrenew/memories/openclaw)<a href="https://agentmods.dev/skills/webrenew/memories/openclaw"><img src="https://agentmods.dev/badge/skills/webrenew/memories/openclaw.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 | $0.00177 | $0.00954 |
| Opus 5 | $0.00088 | $0.00477 |
| Sonnet 5 | $0.00035 | $0.00191 |
| Haiku 4.5 | $0.00018 | $0.00095 |
Grade A, and why
openclaw 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 3d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
openclaw
Canonical setup and operational guidance for OpenClaw + memories.sh.
Quick Start
# First-time setup
openclaw onboard
cd your-project
memories init
memories generate claude -o ~/.openclaw/workspace/AGENTS.md --force
memories generate agents
mkdir -p ~/.openclaw/workspace/skills
if [ -d .agents/skills ]; then cp -R .agents/skills/. ~/.openclaw/workspace/skills/; fi
memories files ingest --global --include-config
memories files apply --global --include-config --force
# Optional: schedule a weekday reminder to run the refresh flow
memories reminders add "0 9 * * 1-5" "OpenClaw refresh: run generate + skills copy + files apply"
Workflow Decision Tree
- If
openclawis missing, stop and direct the user to official OpenClaw install docs. - If OpenClaw was not onboarded on this machine, run first-time setup.
- If setup exists and contract/rules changed, run workspace contract refresh.
- If the task is session lifecycle memory flow, run OpenClaw memory lifecycle commands (
bootstrap,flush,snapshot,sync) in that order as needed. - If behavior appears stale, run verification checks and troubleshooting in order.
- If workspace path is custom, read
~/.openclaw/openclaw.jsonand replace default~/.openclaw/workspacepaths.
Workspace Contract Refresh
cd your-project
memories generate claude -o ~/.openclaw/workspace/AGENTS.md --force
memories generate agents
if [ -d .agents/skills ]; then cp -R .agents/skills/. ~/.openclaw/workspace/skills/; fi
memories files ingest --global --include-config
memories files apply --global --include-config --force
Optional reminder check:
memories reminders list
memories reminders run
Memory Lifecycle Workflow (OpenClaw File Mode)
Use these when session context must persist across resets/compaction:
# 1) Bootstrap semantic + recent episodic context from OpenClaw files
memories openclaw memory bootstrap
# 2) Flush meaningful session events to today's daily log before compaction/reset
memories openclaw memory flush <session-id> --messages 15
# 3) Persist raw session snapshot in DB + OpenClaw snapshot file
memories openclaw memory snapshot <session-id> --trigger reset
# 4) Reconcile DB and OpenClaw files (import/export/both)
memories openclaw memory sync --direction both
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 90 lines · 177 tokens per session scan A d0648b163fe7
openclaw is a skill published in the GitHub repository webrenew/memories (36 stars, last pushed 9d ago), licensed Apache-2.0. It adds 177 tokens to every session and 954 once invoked, about $0.0009 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…