A command for tracing relationships between functions in a codebase. It can find which functions call a given function, which functions it calls, or the path connecting two functions.

Use it to find callers, callees, or a call path between two named functions, with optional directory or file details when names are duplicated.

It reduces the time spent manually following code across files when investigating behavior or assessing the impact of a change.

call-graph — Command by Helweg

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/helweg/open-codebase-index/call-graph

Clone the repo

git clone --depth 1 https://github.com/Helweg/open-codebase-index

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 391 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.

Model	Per session	Once invoked
Fable 5	$0.00012	$0.00391
Opus 5	$0.00006	$0.00196
Sonnet 5	$0.00002	$0.00078
Haiku 4.5	$0.00001	$0.00039

Measured yesterday against content hash dc99ce9eacde, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

call-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 yesterday.

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/call-graph.md · 30 lines

What it actually says

Trace function dependencies using the call_graph and call_graph_path tools.

User input: $ARGUMENTS

Interpret input as follows:

If input asks for a path, connection, route, chain, or "from X to Y", use call_graph_path.
Default to direction="callers" unless input asks for callees/calls/makes calls.
name=<function> or plain text function name sets name.
Unique names resolve automatically for both directions. Use optional filePath=<path> only when duplicate names are reported.
symbolId=<id> remains an optional backward-compatible escape hatch.
For path queries, parse from=<function>, to=<function>, and optional maxDepth=<number>.

Execution flow:

If input asks for a path and has source/target names, call call_graph_path with { from, to, maxDepth? }.
If direction is callers, call call_graph with { name, direction: "callers" }.
If direction is callees, call call_graph with { name, direction: "callees" }.
If the tool reports duplicate names, retry with the suggested filePath; for paths use fromFilePath or toFilePath.

Examples:

/call-graph Database → callers for Database
/call-graph callers name=Indexer → callers for Indexer
/call-graph callees name=Database filePath=src/database.ts → callees for a duplicate name at that location
/call-graph path from=createOrder to=chargeCard → shortest known path between the two symbols

If output says no callers found, suggest running /index force first.

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.

yesterday First seen · 30 lines · 12 tokens per session scan A dc99ce9eacde

Subscribe to this mod's changes

call-graph is a command published in the GitHub repository Helweg/open-codebase-index (183 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 391 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.

Languages Research claude-code code-search codebase-indexing codex embeddings mcp

call-graph

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

rp-build-cli

rp-investigate-cli

rp-oracle-export-cli

rp-reminder-cli

merge

codesage-review