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/danielsimonjr/memory-mcp/migrategit clone --depth 1 https://github.com/danielsimonjr/memory-mcpWrote 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/commands/danielsimonjr/memory-mcp/migrate)<a href="https://agentmods.dev/commands/danielsimonjr/memory-mcp/migrate"><img src="https://agentmods.dev/badge/commands/danielsimonjr/memory-mcp/migrate.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.00340 |
| Opus 5 | $0.00005 | $0.00170 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
MIGRATE 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 4d 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
Migrate Storage Format
Run the migrate-from-jsonl-to-sqlite tool to convert between JSONL and SQLite storage formats.
Instructions
- Run the migration tool:
C:\mcp-servers\memory-mcp\tools\migrate-from-jsonl-to-sqlite\migrate-from-jsonl-to-sqlite.exe $ARGUMENTS
-
The tool automatically detects format based on file extension:
.jsonl,.json→ JSONL format.db,.sqlite,.sqlite3→ SQLite format
-
Migration includes verification step to ensure data integrity.
Options
--from, -f <path>- Source file path--to, -t <path>- Target file path--verbose, -v- Show detailed progress
Usage Examples
# JSONL to SQLite
/project:MIGRATE --from memory.jsonl --to memory.db
# SQLite to JSONL
/project:MIGRATE --from memory.db --to memory.jsonl
# With verbose output
/project:MIGRATE -f memory.jsonl -t memory.db -v
# Positional arguments also work
/project:MIGRATE memory.jsonl memory.db
Notes
- Target file will be created if it doesn't exist
- Existing target file will be overwritten
- Saved searches and tag aliases are stored separately and NOT migrated
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.
- 4d ago First seen · 52 lines · 10 tokens per session scan A 6150b578a6ce
MIGRATE is a command published in the GitHub repository danielsimonjr/memory-mcp (3 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 340 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-31.
Other commands, from other repositories
v-memory-refresh
(Re)index docs/superpowers prose into the local V-memory cache so recall is current. Incremental by file hash; runs fully offline (FTS5, pure stdlib). Optionally enable the semantic lane with a one-time bootstrap. Run it after pulling new docs, or when /v:remember looks stale.
wiki
Build, query, and maintain long-lived knowledge bases. Each wiki = markdown folder + SQLite FTS5 shadow index. Survives sessions, indexes auto-load on SessionStart.
audit-memory
Run a health audit on the ClaudeMemory database and walk the user through resolving findings. Detects inconsistencies (open conflicts, single-cardinality contract violations, recurring contamination), regressions (shortcut filters losing predicate semantics), and optimizations (auto-memory files not yet imported…
reflect
Reflect on an outcome to update memory confidence and create relationships in the central Gnosys database.
memos
Open the kimi-memos-dashboard in the default browser. The dashboard is a read-only web view of every kimi-memory SQLite database.
setup-table
Create a new memory table in Turso for a specific use case.