graph

A command that follows recorded links from one memory to related memories, up to three steps away, and displays them as a tree.

In plain words
What is it for?
Use it to explore relationships such as which memory replaced another or which note came from another source.
Why use it?
It helps you see how stored notes are connected without opening and comparing them one by one. If no links exist, it points you toward a search for similar content.

Command

Part of the m3 plugin — 16 skills, 15 commands, 2 agents, 3 hooks, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add commands/skynetcmd/m3-memory/graph
Clone the repo
git clone --depth 1 https://github.com/skynetcmd/m3-memory

Or install m3, the plugin that ships this one along with the rest of its 16 skills, 15 commands, 2 agents, 3 hooks, 1 MCP server.

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 132 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00132
Opus 5 $0.00010 $0.00066
Sonnet 5 $0.00004 $0.00026
Haiku 4.5 $0.00002 $0.00013

Measured 3d ago against content hash 36dbffeb47d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 3d 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.

commands/graph.md · 12 lines

What it actually says

Call m3:memory_graph with id="$ARGUMENTS", depth=2.

Render as an indented tree: the root memory at the top, each related memory underneath with the relationship type and direction (→ supersedes, ← derived_from, etc.). Truncate content to 80 chars per node.

If the result is empty, the memory has no recorded relationships yet. Suggest /m3:search for content-similar items instead.

Changes

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.

  1. 3d ago First seen · 12 lines · 20 tokens per session scan A 36dbffeb47d7

Subscribe to this mod's changes

graph is a command published in the GitHub repository skynetcmd/m3-memory (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 20 tokens to every session and 132 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.