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/mem0ai/mem0/memory-dreamnpx skills add mem0ai/mem0 --skill memory-dreamgit clone --depth 1 https://github.com/mem0ai/mem0Wrote 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/mem0ai/mem0/memory-dream)<a href="https://agentmods.dev/skills/mem0ai/mem0/memory-dream"><img src="https://agentmods.dev/badge/skills/mem0ai/mem0/memory-dream.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.00058 | $0.01320 |
| Opus 5 | $0.00029 | $0.00660 |
| Sonnet 5 | $0.00012 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
memory-dream 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 4d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Consolidation
You are performing a memory consolidation pass. Your goal is to review all stored memories for this user and improve their overall quality. Think of this as compressing raw observations into clean, durable knowledge.
Available Tools
memory_search
Semantic search across stored memories.
query(required): search querylimit: max resultsuserId,agentId: scope overridesscope:"all"(default),"session", or"long-term"categories: filter by category array
memory_add
Store new facts in long-term memory.
facts(required): array of facts — ALL must share the same categorycategory:"identity","preference","decision","rule","project","configuration","technical","relationship"importance: 0.0–1.0
memory_get
Retrieve a single memory by ID.
memoryId(required): the memory ID
memory_list
List all stored memories for a user or agent.
userId,agentId: scope overridesscope:"all"(default),"session", or"long-term"
memory_update
Update an existing memory's text in place. Atomic and preserves edit history.
memoryId(required): the memory ID to updatetext(required): the new text (replaces old)
memory_delete
Delete memories by ID, query, or bulk.
memoryId: specific memory ID to deleteall: delete ALL memories (requiresconfirm: true)userId,agentId: scope overrides
memory_event_list
List recent background processing events (platform mode only).
memory_event_status
Get status of a specific background event.
event_id(required): the event ID to check
Follow these four phases in order. Do not skip phases.
Phase 1: Orient
Survey the current memory landscape before making any changes.
- Call
memory_listto load all stored memories. - Count memories by category. Note the total.
- Identify the oldest and newest memories by their timestamps.
- Note any obvious problems visible in the list: duplicates, very short entries, entries without temporal anchors.
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.
- 4d ago First seen · 151 lines · 58 tokens per session scan A 1f7abb2151b7
memory-dream is a skill published in the GitHub repository mem0ai/mem0 (64,662 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 1,320 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-30.
Other skills, from other repositories
browserwing-executor
Control browser automation through HTTP API. Supports page navigation, element interaction (click, type, select), data extraction, accessibility snapshot analysis, screenshot, JavaScript execution, and batch operations.
dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website"…
ask-user-question
Ask users questions via the UI. Use when you need clarification, user preferences, or confirmation before proceeding. The user CANNOT see CLI output - this tool is the ONLY way to communicate with them.
memos-memory-guide
Use the MemOS Local memory system to search and use the user's past conversations. Use this skill whenever the user refers to past chats, their own preferences or history, or when you need to answer from prior context. When auto-recall returns nothing (long or unclear user query), generate your own short search query…
browserwing-admin
Manage and operate BrowserWing — an intelligent browser automation platform. Install dependencies, configure LLM, create/manage/execute automation scripts, use AI-driven exploration to generate scripts, browse the script marketplace, and troubleshoot issues.
safe-file-deletion
Enforces explicit user permission before any file deletion. Activates when you're about to use rm, unlink, fs.rm, or any operation that removes files from disk. MUST be followed for all delete operations.