mem0 is memory infrastructure that lets AI agents and applications store and retrieve information across interactions. It supports agents and developers who need persistent context for AI systems.
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-triagenpx skills add mem0ai/mem0 --skill memory-triagegit 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-triage)<a href="https://agentmods.dev/skills/mem0ai/mem0/memory-triage"><img src="https://agentmods.dev/badge/skills/mem0ai/mem0/memory-triage.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.04783 |
| Opus 5 | $0.00029 | $0.02391 |
| Sonnet 5 | $0.00012 | $0.00957 |
| Haiku 4.5 | $0.00006 | $0.00478 |
Grade A, and why
memory-triage 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 5d 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Protocol
You have persistent long-term memory powered by mem0. After responding to the user, evaluate this turn for durable, actionable facts worth persisting across future sessions.
Your primary role is to extract relevant pieces of information from the conversation and organize them into distinct, manageable facts. This allows for easy retrieval and personalization in future interactions.
The core question: "Would a new agent — with no prior context — benefit from knowing this?" If no → do nothing. Most turns produce zero memory operations. That is correct and expected.
Available Tools
memory_search
Semantic search across stored memories.
query(required): search querylimit: max results (default: configured topK)userId,agentId: scope overridesscope:"all"(default),"session", or"long-term"categories: filter by category arrayfilters: advanced filter object
memory_add
Store new facts in long-term memory.
facts(required): array of facts to store — ALL must share the same categorytext: alternative single-fact stringcategory:"identity","preference","decision","rule","project","configuration","technical","relationship"importance: 0.0–1.0 (omit for category default)userId,agentId: scope overridesmetadata: additional key-value metadatalongTerm: true (default) for persistent, false for session-scoped
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 deletequery: search query to find and delete matching memoriesall: delete ALL memories (requiresconfirm: true)confirm: safety gate for bulk operationsuserId,agentId: scope overrides
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.
- 5d ago First seen · 390 lines · 58 tokens per session scan A df46208fe56f
memory-triage is a skill published in the GitHub repository mem0ai/mem0 (64,707 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 4,783 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
pinecone-research
Agent RAG and long-term memory with Pinecone.
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.
langchain-orchestration
Comprehensive guide for building production-grade LLM applications using LangChain's chains, agents, memory systems, RAG patterns, and advanced orchestration.
honcho
Configure and troubleshoot Honcho memory for Hermes.
openclaw-migration
Import an OpenClaw setup (memories, skills) into Hermes.
qdrant
Vector search engine for production RAG systems.