mem0-scope

A setting tool for choosing where saved memories belong: the current project, the current session, or all projects.

In plain words
What is it for?
Use it to view or change the default memory scope for saving and searching.
Why use it?
It prevents memories from being shared too broadly or kept too narrowly when the default location is not appropriate.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/mem0ai/mem0/mem0-scope
Any agent
npx skills add mem0ai/mem0 --skill mem0-scope
Clone the repo
git clone --depth 1 https://github.com/mem0ai/mem0

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,149 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00052 $0.01149
Opus 5 $0.00026 $0.00575
Sonnet 5 $0.00010 $0.00230
Haiku 4.5 $0.00005 $0.00115

Measured yesterday against content hash 61e857edf724, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mem0-scope 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 yesterday.

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.

integrations/mem0-plugin/.opencode-plugin/opencode-skills/mem0-scope/SKILL.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mem0 Scope

View or change the default memory scope — the scope the memory tools use when no explicit scope is given. The setting persists in ~/.mem0/settings.json (default_scope) and the plugin reads it fresh on each memory operation, so a change takes effect immediately in the current session.

The three scopes:

  • project (default) — this repo only. Filters by user_id + app_id.
  • session — this run only. Adds run_id (the current session) so memories are isolated to this conversation.
  • global — across ALL your projects. Reads use app_id="*"; writes drop app_id so the memory is user-wide.

Execution

Step 1: Determine intent

Look at the user's message for a target scope word: project, session, or global (also accept "repo"→project, "run"→session, "all"/"everywhere"→global).

  • No target word present → View mode (Step 2).
  • A target word present → Change mode (Step 3).

Step 2: View mode — show the current scope

  1. Read the current default scope from settings:

    _S="$HOME/.mem0/settings.json"
    [ -f "$_S" ] && grep -o '"default_scope"[[:space:]]*:[[:space:]]*"[a-z]*"' "$_S" | grep -o '[a-z]*"$' | tr -d '"' || echo "project"
    

    If the command prints nothing, the scope is project (the default).

  2. (Optional) Show how many memories live in the current scope by calling get_memories with scope="<current>", page_size=1, and reading the count (or result length) from the response.

  3. Display using the identity the plugin exported (do NOT re-shell git):

    Mem0 memory scope
    
    Current default scope: <current>
    
      project  - this repo only (user + app_id)        <marker if active>
      session  - this run only (adds run_id)           <marker if active>
      global   - all your projects (app_id = *)         <marker if active>
    
    User:    ${MEM0_USER_ID}
    Project: ${MEM0_APP_ID}
    Session: ${MEM0_SESSION_ID}
    
    To change: /mem0-scope session    (or project / global)
    

Read the full file on GitHub · 120 lines

Changes

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.

  1. yesterday First seen · 120 lines · 52 tokens per session scan A 61e857edf724

Subscribe to this mod's changes

mem0-scope is a skill published in the GitHub repository mem0ai/mem0 (64,360 stars, last pushed 3d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,149 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.

Related

Other skills, from other repositories

mcp-apps-builder

MANDATORY for ALL MCP server work - mcp-use framework best practices and patterns. READ THIS FIRST before any MCP server work, including: Creating new MCP servers Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) Debugging MCP server issues or errors Reviewing MCP server code for…

Shubhamsaboo/awesome-llm-apps · 139 tokens

project-graveyard

Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…

Shubhamsaboo/awesome-llm-apps · 127 tokens

commit-archaeologist

Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite…

Shubhamsaboo/awesome-llm-apps · 82 tokens

dependency-doctor

Checks requirements.txt, pyproject.toml, and package.json dependency manifests for surface-level direct-dependency footguns: standard-library shadowing pins, abandoned backports, unpinned dependencies, and obvious intra-manifest conflicts, plus opt-in PyPI yanked releases. Use when the user asks to check a manifest…

Shubhamsaboo/awesome-llm-apps · 115 tokens

scope-creep-detector

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too…

Shubhamsaboo/awesome-llm-apps · 98 tokens

chatgpt-app-builder

DEPRECATED: This skill has been replaced by mcp-app-builder. Check if mcp-app-builder is available in the skills folder. If not, install it: npx skills install mcp-use/mcp-use --skill mcp-app-builder Use mcp-app-builder instead of this skill. Build ChatGPT apps with interactive widgets using mcp-use and OpenAI Apps…

Shubhamsaboo/awesome-llm-apps · 129 tokens