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.
git 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/commands/studiomeyer-io/studiomeyer-marketplace/memory-setup)<a href="https://agentmods.dev/commands/studiomeyer-io/studiomeyer-marketplace/memory-setup"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/memory-setup.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.1 | $0.00014 | $0.00263 |
| Opus 5 | $0.00007 | $0.00131 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade B, and why
memory-setup scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
5. Ask permission BEFORE writing or editing any user config file (`~/.claude/settings.json`, `claude_desktop_config.json`, etc). What it actually says
Help the user set up StudioMeyer Memory autopilot for the AI client they are currently using (Claude Code, Claude Desktop, Cursor, VS Code Copilot Chat, Codex, etc).
- Call
nex_guidefrom thestudiomeyer-memoryMCP server withtopic: "quickstart"to load the latest setup recipe. - Then call
nex_guidewithtopic: "autopilot"for the hook-based automation (SessionStart hook + Stop hook + memory policy). - Detect the user's current client from conversation context. If unclear, ask once.
- Walk the user through the client-specific steps:
- Adding the MCP server (URL:
https://memory.studiomeyer.io/mcp) - First-time OAuth via Magic Link to their email
- Optional: SessionStart and Stop hooks that auto-call
nex_session_startandnex_session_end
- Adding the MCP server (URL:
- Ask permission BEFORE writing or editing any user config file (
~/.claude/settings.json,claude_desktop_config.json, etc). - After setup, call
nex_session_startonce to verify the connection works.
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.
- 6d ago First seen · 16 lines · 14 tokens per session scan B d37e9ca17f9f
memory-setup is a command published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 263 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
pane
Open the Engram graph pane — make sure the machine core is running and share the URL.
save
Manually save current context as a memo to the memex vault.
digest
Digest this project into Engram — an explicit, one-time ingestion of the current working tree into typed memory nodes.
status
Show memex statistics and status including projects, memos, and pending items.
log
Command "log" from allenc84/sapience, covering /log — judgment ledger command, routing, new assessment: /log, review: /log review [domain] and resolve: /log resolve.
recall
Search the engineering memlog and inject the top matching prior lessons. Use when you suspect a recurring issue.