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/lh8ppl/core-memory-kit/bootstrapnpx skills add LH8PPL/core-memory-kit --skill bootstrapgit clone --depth 1 https://github.com/LH8PPL/core-memory-kitWhat 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.00066 | $0.00813 |
| Opus 5 | $0.00033 | $0.00407 |
| Sonnet 5 | $0.00013 | $0.00163 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
bootstrap 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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bootstrap
Purpose
Scaffold the memory-system files into the user's current project. The plugin itself ships with the hooks and skill, but the user's project needs its own context/ directory tree, scripts/ for the auto-extract helper to read project-relative paths, and the cron job declarations.
Steps
-
Check the current project directory (
CLAUDE_PROJECT_DIRor pwd) for an existingcontext/directory.- If exists: ASK the user "context/ already exists. Run bootstrap anyway (skipping existing files)?" Default to yes if no answer.
-
Create directories (idempotent):
context/memory context/sessions context/transcripts scripts cron/jobs -
For each template file in the plugin's
context-template/directory, copy into the user'scontext/if the destination doesn't already exist. Substitute{{TODAY}}with today's date and{{PROJECT_NAME}}with the project's basename.Files to scaffold:
USER.md.template→context/USER.mdMEMORY.md.template→context/MEMORY.mdSOUL.md.template→context/SOUL.mdmemory/INDEX.md.template→context/memory/INDEX.mdSETUP.md→context/SETUP.md(no substitution)
-
Operational scripts — v0.1.0 ships these as Node bins inside the published
@lh8ppl/core-memory-kitnpm package, NOT as plugin-copied scripts. Users invoke them viacmksubcommands:cmk daily-distill(was:run-daily-distill.sh)cmk weekly-curate(was:run-weekly-curate.sh)cmk compress --lazy(no-cron fallback; new in Task 35)cmk register-crons(was:register-crons.py)
-
Copy cron job declarations from the plugin's
cron-template/jobs/into the user'scron/jobs/:daily-memory-distill.mdweekly-memory-curator.md
-
Report: list which files were created vs skipped. Then tell the user:
- Open
context/SETUP.mdfor the Layer 6 (crons) install steps - Open
INSTALL-<your-os>.mdfrom the kit repo for OS prerequisites - The plugin's hooks already activate on session start — no per-project hook registration needed
- Open
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.
- 2d ago First seen · 65 lines · 66 tokens per session scan A d331c4868321
bootstrap is a skill published in the GitHub repository LH8PPL/core-memory-kit (6 stars, last pushed 5d ago), licensed MIT. It adds 66 tokens to every session and 813 once invoked, about $0.0003 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
Effective Memory
The essential habits for an AI agent with memory — session bookends, learning triggers, verification, safety, and the operational discipline that turns raw recall into compounding intelligence. Pinned, always-injected.
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.
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.
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…