graph

A code-navigation command that shows where a named symbol is defined and referenced, grouped by file.

In plain words
What is it for?
Use it to trace callers, find affected files before editing code, and inspect short snippets around each reference.
Why use it?
It helps you understand how a function, class, or variable is connected to the rest of an indexed project. It can also show when a defined symbol is unused.

Command

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/s1lv4/th0th/graph
Clone the repo
git clone --depth 1 https://github.com/S1LV4/th0th
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 250 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.00012 $0.00250
Opus 5 $0.00006 $0.00125
Sonnet 5 $0.00002 $0.00050
Haiku 4.5 $0.00001 $0.00025

Measured 2d ago against content hash 839e88014dff, 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 2d 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.

apps/claude-plugin/commands/graph.md · 17 lines

What it actually says

Show the reference graph for $ARGUMENTS.

Steps:

  1. Resolve projectId from cwd (th0th_list_projects match by path basename).
  2. Call mcp__th0th__th0th_go_to_definition with symbolName=$ARGUMENTS to locate the definition first.
  3. Call mcp__th0th__th0th_get_references with the same symbolName (and fqn if provided by the definition lookup).
  4. Group the results by file, sorted by reference count descending.
  5. For each file, list line — ref_kind — context snippet (keep snippet to 1 line).

If 0 references, the symbol might be defined but unused — note that. If 0 definitions and 0 references, the name might be case-sensitive or a FQN is needed.

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. 2d ago First seen · 17 lines · 12 tokens per session scan A 839e88014dff

Subscribe to this mod's changes

graph is a command published in the GitHub repository S1LV4/th0th (135 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 250 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.