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-show-graph)<a href="https://agentmods.dev/commands/studiomeyer-io/studiomeyer-marketplace/memory-show-graph"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/memory-show-graph/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/commands/studiomeyer-io/studiomeyer-marketplace/memory-show-graph"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/memory-show-graph.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.00020 | $0.00278 |
| Opus 5 | $0.00010 | $0.00139 |
| Sonnet 5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
memory-show-graph 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
Render the user's StudioMeyer Memory knowledge graph as an interactive 3D force-graph.
- Call
nex_graph_viewfrom thestudiomeyer-memoryMCP server.- If
$ARGUMENTSis provided, pass it asentityId(or as a name to search first vianex_entity_searchand use the resolved id) plusdepth: 2. - If no argument, call without args. The server returns the global graph.
- If
- The host either renders the interactive 3D view inline (MCP Apps capable hosts: claude.ai Web/Desktop, VS Code Copilot Chat, Goose, Postman, MCPJam) OR returns the structured JSON with entities, relations and stats. Both behaviors are correct.
- Summarize what came back in two lines: number of entities, number of relations, dominant entity types. Do not invent any node that is not in the response.
- If the host rendered the view, tell the user they can hover a node to pin its detail panel, drag to rotate, scroll to zoom, and use the time-travel slider to see the graph as of a past date.
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 Changed 417397c60eea
- 9d ago First seen · 14 lines · 20 tokens per session scan A 510ef65aecb8
memory-show-graph is a command published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 278 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
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.
status
Show memex statistics and status including projects, memos, and pending items.
digest
Digest this project into Engram — an explicit, one-time ingestion of the current working tree into typed memory nodes.
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.