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 skills add mnemon-dev/mnemon --skill containergit clone --depth 1 https://github.com/mnemon-dev/mnemonWrote 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/mnemon-dev/mnemon/container)<a href="https://agentmods.dev/skills/mnemon-dev/mnemon/container"><img src="https://agentmods.dev/badge/skills/mnemon-dev/mnemon/container/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mnemon-dev/mnemon/container"><img src="https://agentmods.dev/badge/skills/mnemon-dev/mnemon/container.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00029 | $0.01165 |
| Opus 5.5 | $0.00012 | $0.00466 |
| Sonnet 5.5 | $0.00006 | $0.00233 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
mnemon 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 1mo 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mnemon — Persistent Memory
Memory Stores
- Private (default): Per-group, read-write. All writes go here.
- Global: Shared across all groups, read-only. Use
--store global --readonlyto query.
Recall — before responding
Default: recall on every new user message, unless ALL of these apply:
- Direct follow-up within a topic already fully in context
- No reference to past sessions, decisions, or preferences
- No knowledge dependency beyond the current conversation
To recall:
mnemon recall "<query>" --limit 5
# Also check shared knowledge:
mnemon recall "<query>" --store global --readonly --limit 5
Craft a focused, keyword-rich query — do not pass the raw user prompt.
Remember — after responding
Run this decision tree after every substantive response:
Step 1 — Does this exchange contain any of these? a) User directive — preference, decision, correction, explicit "remember this" b) Reasoning conclusion — non-trivial judgment from multi-source synthesis c) Durable observed state — system fact, environment detail, architectural finding → No to all → STOP.
Step 2 — Does a highly overlapping memory already exist? → Yes, incremental new info → STORE the new content; review the existing memory separately → Yes, but contradicts/supersedes → STORE and verify the new fact; explicitly forget the old ID only if superseded → No significant overlap → CREATE
Step 3 — Is it worth storing? Rebuilding from scratch costs more than storing + recalling?
- Single-query public facts → No
- Multi-source synthesis with non-obvious conclusions → Yes
- User-specific context no search engine can recover → Yes → No → STOP.
What to store: conclusions and user-specific context, not raw facts.
Workflow
- Remember:
mnemon remember "<fact>" --cat <cat> --imp <1-5> --entities "e1,e2" --source agent- Only exact content repeats are skipped; distinct content is stored and diff suggestions are advisory.
- To retire a superseded memory, store and verify the new fact, then explicitly run
mnemon forget <old-id>. - Output includes
action(added/skipped),semantic_candidates,causal_candidates.
- Link (evaluate candidates from step 1 — use judgment, not mechanical rules):
- Review
causal_candidates: does a genuine cause-effect relationship exist?causal_signalis regex-based and prone to false positives — only link if the memories are truly causally related. - Review
semantic_candidates: are these memories meaningfully related? Highsimilarityalone is not sufficient — skip candidates that share keywords but discuss unrelated topics. - Syntax:
mnemon link <id> <candidate> --type <causal|semantic> --weight <0-1> [--meta '<json>']
- Review
- Recall:
mnemon recall "<query>" --limit 10
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.
- 1mo ago Changed · +18 lines 6a41a8125d85
- 1mo ago First seen · 87 lines · 29 tokens per session scan A 9dd3a80a36a5
mnemon is a skill published in the GitHub repository mnemon-dev/mnemon (641 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 1,165 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
innate-memory
Innate procedural knowledge layer for coding, debugging, and analysis sessions. ACTIVATE when: (1) user says "remember", "save", "log", "follow this rule", "don't forget", "recall", or "what did we learn"; (2) a non-obvious solution, workaround, constraint, or invariant was discovered during this session; (3) starting…
innate-memory
Innate procedural knowledge layer for coding, debugging, and analysis sessions. ACTIVATE when: (1) user says "remember", "save", "log", "follow this rule", "don't forget", "recall", or "what did we learn"; (2) a non-obvious solution, workaround, constraint, or invariant was discovered during this session; (3) starting…
kayba-ace
This skill ships learnfromtraces.py, a script that reads OpenClaw session transcripts, feeds them through the ACE learning pipeline, and writes an updated skillbook to disk.
brain-setup
Bootstrap the Open Project Brain Standard into the current project — prefer brain init (ensure BRAIN.md, scaffold empty brain brainRoot-aware, default-wire CLAUDE.md + AGENTS.md). Optionally install a pre-commit hook and a Claude Code or Codex SessionStart hook.
brain-page
Operating manual for reading and writing a project's brain — every read and write goes through the bundled zero-dependency brain CLI; never hand-edit brain files. Read it before creating or modifying any page or root page.
brain-bootstrap
Seed a freshly-scaffolded brain with real project knowledge — on an existing (brownfield) project read the code, docs, and git log to draft the six root pages and capture key historical decisions; on a near-empty (greenfield) project interview the user. Every write goes through the brain CLI. Run it after brain-setup.