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/memories-clinpx skills add webrenew/memories --skill memories-cligit clone --depth 1 https://github.com/webrenew/memoriesWhat 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.00158 | $0.01728 |
| Opus 5 | $0.00079 | $0.00864 |
| Sonnet 5 | $0.00032 | $0.00346 |
| Haiku 4.5 | $0.00016 | $0.00173 |
Grade A, and why
memories-cli 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
memories-cli
CLI reference for @memories.sh/cli — manage memories, generate configs, and sync across tools.
The CLI is the primary way to interact with memories.sh. Use it to store memories, generate native config files, and manage your memory store. For environments where the CLI isn't available (v0, bolt.new, Lovable, or other browser-based agents), use the MCP server as a fallback.
Install & Init
npm install -g @memories.sh/cli # or: npx @memories.sh/cli
memories init # Initialize in current project
memories init auto-detects AI tools (Claude Code, Cursor, Windsurf, VS Code) and configures MCP + generates instruction files.
Command Quick Reference
| Command | Purpose |
|---|---|
memories add <content> |
Store a memory |
memories recall |
Context-aware memories for current project |
memories search <query> |
Full-text search |
memories list |
List memories with filters |
memories edit <id> |
Edit content, type, or tags |
memories forget <id> |
Soft-delete a memory |
memories generate |
Generate AI tool config files |
memories prompt |
Generate a system prompt |
memories serve |
Start MCP server |
memories session <subcommand> |
Manage explicit sessions (start, checkpoint, status, end, snapshot) |
memories compact run |
Run inactivity compaction worker |
memories consolidate run |
Merge duplicates and supersede stale truths |
memories openclaw memory <subcommand> |
OpenClaw file-mode workflows (bootstrap, flush, snapshot, sync) |
memories reminders |
Manage cron reminders (add, list, run, enable, disable, delete) |
Core Workflows
1. New Project Setup
cd my-project
memories init # Detect tools, configure MCP, generate files
memories add "Use pnpm" --type rule
memories add "Chose Supabase for auth" --type decision
memories generate # Update all AI tool configs
What ships with it
2 files 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 · 178 lines · 158 tokens per session scan A dbdac3f83955
memories-cli is a skill published in the GitHub repository webrenew/memories (36 stars, last pushed 9d ago), licensed Apache-2.0. It adds 158 tokens to every session and 1,728 once invoked, about $0.0008 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…