mnemos-memory

mnemos-memory is a skill for Claude Code, Codex from ncz-os/mnemos. It costs 82 tokens per session (1,032 once invoked), scanned A, original, Apache-2.0.

A skill for reading and writing persistent project memory through the MNEMOS service. It covers recalling and saving decisions, infrastructure facts, project context, solutions, patterns, and standards across agent sessions.

In plain words
What is it for?
Use it to search prior project knowledge before making decisions and save useful findings, fixes, architecture decisions, or team conventions for later sessions.
Why use it?
It helps an agent recover relevant context from earlier sessions instead of repeating research or forgetting established choices.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to search prior project knowledge before making decisions and save useful findings, fixes, architecture decisions, or team conventions for later sessions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ncz-os/mnemos/mnemos-memory
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.

Any agent
npx skills add ncz-os/mnemos --skill mnemos-memory
Clone the repo
git clone --depth 1 https://github.com/ncz-os/mnemos

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mnemos-memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/ncz-os/mnemos/mnemos-memory.svg)](https://agentmods.dev/skills/ncz-os/mnemos/mnemos-memory)
Your own site
<a href="https://agentmods.dev/skills/ncz-os/mnemos/mnemos-memory"><img src="https://agentmods.dev/badge/skills/ncz-os/mnemos/mnemos-memory.svg" alt="Measured on agentmods" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,032 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00082 $0.01032
Opus 5 $0.00041 $0.00516
Sonnet 5 $0.00016 $0.00206
Haiku 4.5 $0.00008 $0.00103

Measured 8d ago against content hash 5782f0a775da, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

mnemos-memory 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 8d 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.

integrations/openclaw/.agents/skills/mnemos-memory/SKILL.md · 90 lines

How it starts

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

MNEMOS Memory

MNEMOS is persistent memory shared across agent sessions. It is a network service, not a prompt. Reads and writes happen through the mnemos MCP server.

When to search MNEMOS

Before you commit to an approach on any of these, run a quick search_memories:

  • Infrastructure — ports, hostnames, service locations, credential storage layout
  • Decisions — architecture choices, tradeoffs the team has already settled
  • Solutions — workarounds for known bugs, fixes already applied elsewhere
  • Patterns — reusable approaches already validated
  • Projects — current project state, owners, milestones
  • Standards — conventions, quality gates, review criteria

If the user's task looks like something that might have been solved before, search first. One query is cheap; wasted work is not.

Search patterns

  • Start broad with full-text: search_memories(query="topic keywords", limit=10) before narrowing
  • Filter by category when you know the domain: search_memories(query="auth flow", category="decisions")
  • Use semantic search for concept-level matches: search_memories(query="...", semantic=true)
  • Large context loads: use POST /v1/memories/rehydrate directly via the REST API (this path is not an MCP tool in the current mnemos.mcp.stdio bridge). Chain multiple search_memories calls with a running token tally if you need to stay within MCP.

When to store

Store after:

  • Solving a non-trivial problem (store the solution and the failure mode, not just the fix)
  • Making an architectural decision with rationale (use category=decisions; include why and tradeoffs)
  • Discovering infrastructure shape (endpoint, port, auth scheme) that future sessions will need
  • Establishing a pattern that other agents should follow (category=patterns or standards)

Do not store:

  • Session transcripts (the session ingest endpoint handles that separately)
  • Temporary state that will be stale in a day
  • Information the user will see in the diff (recent commits, current branch)

Read the full file on GitHub · 90 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. 8d ago First seen · 90 lines · 82 tokens per session scan A 5782f0a775da

Subscribe to this mod's changes

mnemos-memory is a skill published in the GitHub repository ncz-os/mnemos (31 stars, last pushed yesterday), licensed Apache-2.0. It adds 82 tokens to every session and 1,032 once invoked, about $0.0004 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

memclaw

The agent's persistent long-term memory — the only knowledge that survives across sessions, shared across the fleet under access control. Consult it at the start of a task to recall prior decisions, findings, and rules before acting, and write outcomes, decisions, and lessons as work completes. Use whenever a caura…

caura-ai/caura · 124 tokens

company-brain

How an agent should operate as one mind inside a shared Company Brain built on Caura — recall before acting, obey fleet keystones, reuse and publish skills, and report outcomes so every task compounds across the whole organization. Use this whenever you work as part of a Caura-connected team or fleet and your work…

caura-ai/caura · 108 tokens

kb-research

Structured approach to finding and synthesizing information from the user's knowledge base.

MODSetter/SurfSense · 17 tokens

gsd-resume-work

Resume work from previous session with full context restoration.

SpillwaveSolutions/agent-brain · 15 tokens

ctx

A project-context tool for recording important lessons about bugs and failure-prone code in nearby AGENTS.md documents. These documents give coding agents repository-specific guidance.

yilecoding/fastapi-react-admin · 67 tokens

saferskills

Use SaferSkills to find, evaluate, and safely install AI agent capabilities (skills, MCP servers, hooks, plugins, rules) and to assess a whole agent. Run this before you install, add, recommend, or trust any capability — or when asked whether one is safe or what its score is: scan and score it first with npx…

OpenLatch/saferskills · 91 tokens