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 studiomeyer-io/studiomeyer-marketplace --skill memory-import-guidegit clone --depth 1 https://github.com/studiomeyer-io/studiomeyer-marketplaceWrote 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/studiomeyer-io/studiomeyer-marketplace/memory-import-guide)<a href="https://agentmods.dev/skills/studiomeyer-io/studiomeyer-marketplace/memory-import-guide"><img src="https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/memory-import-guide/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/studiomeyer-io/studiomeyer-marketplace/memory-import-guide"><img src="https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/memory-import-guide.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.00052 | $0.00886 |
| Opus 5 | $0.00026 | $0.00443 |
| Sonnet 5 | $0.00010 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
memory-import-guide 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 5d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Import Guide
StudioMeyer Memory can ingest conversation history from five platforms via nex_import. This skill is the recipe book for each one.
How import works
- Export the conversation history from the source platform to a file on disk.
- Analyze:
nex_importwithaction: "analyze"shows a preview of what would be imported without writing anything. - Confirm the preview with the user.
- Import:
nex_importwithaction: "import"writes sessions, learnings, entities, and decisions into the user's tenant.
Always run analyze first. Imports are append-only but still worth confirming, especially when there are thousands of messages.
Platform-specific export recipes
ChatGPT
- Settings → Data Controls → Export Data
- You get a ZIP by email. Unzip it.
- The file you want is
conversations.json(sometimesconversations.jsonlon newer exports). - Run
nex_importwithplatform: "chatgpt"and the file path.
Claude
- Settings → Account → Export Data
- Unzip. Use
conversations.json. nex_importwithplatform: "claude".
Gemini
- Google Takeout → Select "Gemini" → Export
- You get a ZIP with an HTML or JSON bundle.
nex_importwithplatform: "gemini".
Microsoft Copilot
- Copilot settings → Activity → Export
- JSON file.
nex_importwithplatform: "copilot".
Perplexity
- Perplexity settings → Export conversations
- JSON file.
nex_importwithplatform: "perplexity".
What gets extracted
nex_import uses Haiku (fast, cheap) to extract:
- Sessions: one per conversation, with start/end timestamps from the source
- Learnings: salient facts, insights, and patterns from the conversation
- Entities: people, projects, tools, services mentioned
- Decisions: explicit choices the user made with stated rationale
- Relations: links between extracted entities
The extraction is conservative. It will not invent facts. If a conversation is pure chit-chat, very little will be saved.
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.
- 5d ago Changed 1657c32debff
- 10d ago First seen · 91 lines · 52 tokens per session scan A 09f713226ab6
memory-import-guide is a skill published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 6d ago), licensed MIT. It adds 52 tokens to every session and 886 once invoked, about $0.0003 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 skills, from other repositories
memory-protocol
A shared set of rules for using a persistent memory service across coding-agent sessions.
memory
Activate this skill when starting a new session, beginning a new task, saving knowledge, recalling past decisions, or after completing significant work. Also activate on errors to log them for pattern analysis. Relevant when the user asks about memory, past context, lessons learned, decisions history, project…
engram
Read and write the project's durable reasoning memory (decisions, principles, cautions, problems, insights) through the Engram MCP tools. Recall relevant memory before non-trivial work; capture only durable, high-value knowledge silently at natural stopping points; keep the graph honest (judge suspects, close answered…
engram-digest
Seed or top up this project's Engram graph from the existing codebase — an explicit, user-invoked digestion of the current working tree into typed memory nodes (decisions, principles, cautions, problems, insights, intents). Use when the user says "digest this project", "ingest the codebase into memory", "seed the…
garden-tending
Tend the knowledge garden — diagnose vault health, condense project memos into project.md overviews, create/merge cross-project topics, fix broken links, archive superseded notes, extend trails. Trigger on "tend the garden", "condense", "update project overview", "check vault health", "where are we with X?", "what…
curator-practice
Operating philosophy for autonomous memex curator tending — orientation protocol, signal triage, bounded work units, initiative thresholds, logging conventions. Trigger on cron-launched runs with no user prompt, "use your judgment", "tend without instructions", "do a pass on the vault", "I'll be away — do what needs…