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 commands/rand/mnemosyne/memory-exportgit clone --depth 1 https://github.com/rand/mnemosyneWhat 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.00011 | $0.01026 |
| Opus 5 | $0.00005 | $0.00513 |
| Sonnet 5 | $0.00002 | $0.00205 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
memory-export 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 2d 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.
What it actually says
I will export memories from Mnemosyne to a markdown file for review, backup, or sharing.
Usage:
/memory-export- Export current project to memories-.md/memory-export --namespace <ns>- Export specific namespace/memory-export --output <file>- Export to custom file/memory-export --format <markdown|json>- Export format (default: markdown)/memory-export --all- Export all namespaces
Instructions for me:
-
Parse the arguments:
- Extract
--namespaceflag if present (otherwise auto-detect) - Extract
--outputflag if present - Extract
--formatflag if present (default: "markdown") - Extract
--allflag if present (exports all namespaces)
- Extract
-
Determine namespace:
- If
--allflag: set namespace tonull(all) - If
--namespacespecified: use that - Otherwise auto-detect from git root + CLAUDE.md
- If
-
Fetch memories using MCP:
{ "name": "mnemosyne.list", "arguments": { "namespace": "<namespace or null>", "limit": 1000, "sort_by": "importance" } } -
Determine output filename:
- If
--outputspecified: use that - Otherwise:
memories-<project-name>-<date>.md - Example:
memories-ecommerce-2025-10-26.md
- If
-
Generate markdown content:
# Memory Export - <Namespace> Generated: <date and time> Total Memories: <count> ## Table of Contents - [Architecture Decisions](#architecture-decisions) (<count>) - [Code Patterns](#code-patterns) (<count>) - [Bug Fixes](#bug-fixes) (<count>) - [Configurations](#configurations) (<count>) - [Constraints](#constraints) (<count>) - [Entities](#entities) (<count>) - [Insights](#insights) (<count>) - [References](#references) (<count>) - [Preferences](#preferences) (<count>) --- ## Architecture Decisions ### [<importance>/10] <summary> **ID**: `<memory_id>` **Date**: <created_at> **Tags**: <tags> **Context**: <context> <full content> **Related Files**: - <file> - <file> **Links**: - → <linked memory summary> (<link_type>, strength: <strength>) **Metadata**: - Importance: <importance>/10 - Confidence: <confidence> - Access count: <access_count> - Last accessed: <last_accessed_at> --- <repeat for each memory, grouped by type> -
Generate JSON format (if
--format json):{ "export_date": "<ISO 8601>", "namespace": "<namespace>", "total_memories": <count>, "memories": [ { "id": "<id>", "summary": "<summary>", "content": "<content>", "memory_type": "<type>", "importance": <importance>, ...full memory object... } ] } -
Write to file:
- Use Write tool to create the file
- Confirm to user: "✓ Exported memories to "
-
Format the confirmation:
✓ Exported <count> memories to <filename> Breakdown by type: - Architecture Decisions: <count> - Code Patterns: <count> - Bug Fixes: <count> - Configurations: <count> - Constraints: <count> - Entities: <count> - Insights: <count> - References: <count> - Preferences: <count> File size: <size> KB Format: <markdown|json> You can now review, edit, or share this export file. To re-import (future feature): mnemosyne import <filename> -
Error handling:
- If MCP server not available: "Error: Mnemosyne MCP server not running"
- If no memories found: "No memories found for export"
- If file write fails: "Error: Could not write to : "
Please export the memories with the provided options.
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.
- 2d ago First seen · 143 lines · 11 tokens per session scan A 9ee273645b87
memory-export is a command published in the GitHub repository rand/mnemosyne (84 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 1,026 once invoked, about $0.0001 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 commands, from other repositories
hatch3r-debug
Standalone debug-and-fix workflow — add strategic debug logging, collect runtime logs from the user, perform root cause analysis, implement the fix, and clean up all debug artifacts.
hatch3r-feature-plan
Design a new capability -- draft user stories, acceptance criteria, data model, API surface, and sub-issue breakdown as an epic-shaped todo.md for greenfield features.
hatch3r-bug-plan
Diagnose a complex incident -- reproduce the symptom, rank root-cause hypotheses, design the fix path, and emit regression coverage items as a board-ready investigation.
hatch3r-bug-pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + fix together, then root-cause-depth review -- with full sub-agent delegation.
hatch3r-incident-response
Drive a live production incident through a structured lifecycle -- triage + topology, bounded-autonomy mitigation, stakeholder communication, then a blameless post-mortem with runbook -- via delegated sub-agents.
story-6.1.4
Story ID: 6.1.4 Epic: Epic-6.1 - Agent Identity System Wave: Wave 1 (Foundation) Status: 📋 Ready to Start Priority: 🔴 Critical Owner: Dev (Dex) Created: 2025-01-14 Updated: 2025-01-17 (v4 - Unified System Integration) Duration: 2.5 days (20 hours) Investment: $250.00.