New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Mnemosyne Memory Override

by mnemosyne-oss in mnemosyne-oss/mnemosyne

Hard rule override that forces Mnemosyne for all durable memory storage.

MITAuto-check passedAgent Workflows

Install Mnemosyne Memory Override

skills CLI
$ npx skills add mnemosyne-oss/mnemosyne --skill mnemosyne-memory-override -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mnemosyne-oss/mnemosyne mnemosyne-memory-override --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mnemosyne-oss/mnemosyne.git skills-src && mkdir -p .claude/skills && cp -r skills-src/integrations/hermes/src/mnemosyne_hermes/skills/mnemosyne-memory-override .claude/skills/mnemosyne-memory-override && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mnemosyne-memory-override
GitHub stars
3.4k
Token cost
~630 tokens
SKILL.md length
266 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Hard rule override that forces Mnemosyne for all durable memory storage.

  • Works in 3 steps: Save to Mnemosyne first with… → Then REMOVE the old entry from memory… → This prevents stale duplicates and…
  • Tasks that involve Session handoff
  • SKILL.md covers CRITICAL RULE, Mapping, When to use legacy memory (rare) and Muscle Memory / Reflex Problem, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Mnemosyne Memory Override is an agent skill from mnemosyne-oss/mnemosyne. Hard rule override that forces Mnemosyne for all durable memory storage. The legacy memory tool is DEPRECATED for user preferences, credentials, and project conventions. Use memory ONLY for ephemeral session state.

Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Session handoff. The repository describes itself as: Zero-cloud AI memory that works everywhere. SQLite-backed. One pure-Python dependency. The licence is MIT.

When your agent uses it

  • Tasks that involve Session handoff

Example prompts

  • “/mnemosyne-memory-override”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Save to Mnemosyne first with mnemosyne_remember
  2. Then REMOVE the old entry from memory with memory(action="remove")
  3. This prevents stale duplicates and confusion

What it can do on your machine

Read from SKILL.md and the folder at commit 1a5b645. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mnemosyne Memory Override loads about 630 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 266 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~630

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mnemosyne-oss/mnemosyne at commit 1a5b645, republished under its MIT licence (© mnemosyne-oss). 266 words, ~630 tokens.

Download SKILL.mdSave it as .claude/skills/mnemosyne-memory-override/SKILL.md (or your agent's skills folder).
name
mnemosyne-memory-override
description
Hard rule override that forces Mnemosyne for all durable memory storage. The legacy memory tool is DEPRECATED for user preferences, credentials, and project conventions. Use memory ONLY for ephemeral session state.
trigger
Whenever you would use memory(action="add|replace|remove") for anything that should survive across sessions, STOP and use the Mnemosyne memory tools instead.

Mnemosyne Memory Override

CRITICAL RULE

NEVER use the memory tool for durable facts.

The legacy memory system is deprecated. It has a tiny 2,200 character limit and does not use vector search. Mnemosyne is the single source of truth for all durable user data.

Mapping

Old (FORBIDDEN)New (REQUIRED)
memory(action="add", target="user", ...)mnemosyne_remember(content=..., importance=0.9+, source="preference")
memory(action="add", target="memory", ...)mnemosyne_remember(content=..., importance=0.7+, source="fact")
memory(action="replace", ...)Use the relevant Mnemosyne update flow: recall the current entry, then store corrected content with mnemosyne_remember; use an explicit update tool/flow when the integration exposes one.
memory(action="remove", ...)Use the relevant Mnemosyne invalidation/forget flow: mark the obsolete fact invalid, supersede it with corrected content, or call the integration's forget/remove tool when available. Do not rely on passive aging for known-wrong durable data.

When to use legacy memory (rare)

  • Ephemeral session state (current todo list, temp flags)
  • When Mnemosyne is explicitly confirmed down

Muscle Memory / Reflex Problem

You will reflexively reach for memory out of old habit. This is a known bug in your training. Before EVERY memory tool call, pause and ask:

"Is this durable? Would I want this next session?"

If yes → use Mnemosyne If no (temp flag, todo state) → memory is acceptable

Migration Cleanup

When moving data from legacy memory to Mnemosyne:

  1. Save to Mnemosyne first with mnemosyne_remember
  2. Then REMOVE the old entry from memory with memory(action="remove")
  3. This prevents stale duplicates and confusion

Enforcement

If you catch yourself typing memory(action= for durable data:

  1. CANCEL that tool call
  2. Use Mnemosyne instead
  3. Set importance >= 0.7 for anything that matters later
  4. If you already polluted legacy memory, remove the entry immediately

© mnemosyne-oss, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in integrations/hermes/src/mnemosyne_hermes/skills/mnemosyne-memory-override of mnemosyne-oss/mnemosyne.

Open the folder on GitHubat commit 1a5b645

Compare with similar skills

Mnemosyne Memory Override next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mnemosyne Memory Override compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mnemosyne Memory Override this skillmnemosyne-oss/mnemosyne3.4k—~630Automated safety check: PassMIT
Orca CLIstablyai/orca89k2 repos~593Automated safety check: PassMIT
Beads Task Memorygastownhall/beads28k—~1.2kAutomated safety check: PassMIT
Session History Searchslopus/happy24k—~3.1kAutomated safety check: PassMIT
Paseo Agent Handoffgetpaseo/paseo20k1 repos~606Automated safety check: PassCustom licence
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: NotesCustom licence

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    89k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed

  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Session History Search

    slopus/happy

    Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed

  • Memori Long-Term Memory

    MemoriLabs/Memori

    Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.

    17k GitHub stars~2k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check: notes

  • Beads

    liwp/again

    A skill your agent uses when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory.

    118 GitHub starsUsed in 6 repos~537 tokens
    Agent WorkflowsAuto-check passed

More from mnemosyne-oss/mnemosyne

  • Mnemosyne Context

    mnemosyne-oss/mnemosyne

    Load this when working on the mnemosyne memory system — its repo, sync server, memory databases, or CI.

    3.4k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • No Mistakes

    mnemosyne-oss/mnemosyne

    Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach upstream.

    3.4k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Hermes Memory Providers

    mnemosyne-oss/mnemosyne

    Install and configure Mnemosyne as a Hermes Agent memory provider — local SQLite with vector search, episodic consolidation, and temporal knowledge graphs.

    3.4k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

Categories

Questions about Mnemosyne Memory Override

What does Mnemosyne Memory Override do?

Hard rule override that forces Mnemosyne for all durable memory storage. Mnemosyne Memory Override is an agent skill from mnemosyne-oss/mnemosyne. Hard rule override that forces Mnemosyne for all durable memory storage.

When should I use Mnemosyne Memory Override?

Mnemosyne Memory Override fits situations like: tasks that involve Session handoff.

How do I install Mnemosyne Memory Override in Claude Code?

Run `npx skills add mnemosyne-oss/mnemosyne --skill mnemosyne-memory-override -a claude-code`. Or copy the skill folder (integrations/hermes/src/mnemosyne_hermes/skills/mnemosyne-memory-override in mnemosyne-oss/mnemosyne) into .claude/skills/mnemosyne-memory-override in your project. Claude Code loads it when a task matches its description.

How do I install Mnemosyne Memory Override in Codex?

Run `npx skills add mnemosyne-oss/mnemosyne --skill mnemosyne-memory-override -a codex`. Or copy the skill folder (integrations/hermes/src/mnemosyne_hermes/skills/mnemosyne-memory-override in mnemosyne-oss/mnemosyne) into .agents/skills/mnemosyne-memory-override in your project. Codex loads it when a task matches its description.

Can I use Mnemosyne Memory Override in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mnemosyne-oss/mnemosyne --skill mnemosyne-memory-override -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mnemosyne-memory-override, .gemini/skills/mnemosyne-memory-override, .github/skills/mnemosyne-memory-override and .opencode/skills/mnemosyne-memory-override in your project.

What does Mnemosyne Memory Override need to run?

SKILL.md names no scripts, command-line tools or credentials: Mnemosyne Memory Override is instructions for the agent only.

Does Mnemosyne Memory Override access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mnemosyne Memory Override safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Mnemosyne Memory Override use?

Mnemosyne Memory Override is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mnemosyne Memory Override use?

About 630 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Mnemosyne Memory Override?

Skills that share tags, products or a category with Mnemosyne Memory Override: Orca CLI (stablyai/orca, 89k stars), Beads Task Memory (gastownhall/beads, 28k stars), Session History Search (slopus/happy, 24k stars) and Paseo Agent Handoff (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mnemosyne Memory Override?

mnemosyne-oss (a GitHub organization) maintains it in mnemosyne-oss/mnemosyne, which has 3,377 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 11, 2026.

Source: mnemosyne-oss/mnemosyne on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.