callgraph

A tool that maps which functions in a program call one another, forming a call graph.

In plain words
What is it for?
Analyze a whole module, inspect a function's nearby calls, find paths or reachable functions, identify roots and leaves, and create Mermaid diagrams.
Why use it?
It makes complex code relationships easier to inspect than reading files one by one. It helps reveal entry points, utility functions, recursive groups, and routes between functions.

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/marcosd4h/deepextractruntime/callgraph
Clone the repo
git clone --depth 1 https://github.com/marcosd4h/DeepExtractRuntime
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,393 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.00000 $0.01393
Opus 5 $0.00000 $0.00696
Sonnet 5 $0.00000 $0.00279
Haiku 4.5 $0.00000 $0.00139

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

Security

Grade A, and why

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

commands/callgraph.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Call Graph

Overview

Build, query, and visualize call graphs for a module or function. Shows topology statistics, strongly connected components, hub functions, root/leaf nodes, and generates Mermaid diagrams.

Usage:

  • /callgraph appinfo.dll -- module-wide stats (node/edge counts, hubs, connectivity)
  • /callgraph appinfo.dll --scc -- strongly connected components (recursive call clusters)
  • /callgraph appinfo.dll --roots -- functions with no callers (entry points by graph structure)
  • /callgraph appinfo.dll --leaves -- functions that call nothing (leaf/utility functions)
  • /callgraph appinfo.dll AiLaunchProcess -- neighborhood graph for a specific function
  • /callgraph appinfo.dll AiLaunchProcess --diagram -- Mermaid diagram of the function's call neighborhood
  • /callgraph appinfo.dll --path FuncA FuncB -- find call path between two functions
  • /callgraph appinfo.dll --reachable FuncA -- all functions reachable from FuncA

IMPORTANT: Execution Model

This is an execute-immediately command. Do NOT present anything for user confirmation. Run and write the call graph analysis straight to the chat as your response. The user expects to see the completed output.

Execution Context

IMPORTANT: Any inline Python that imports helpers.* must run with cd <workspace>/.claude (so the .claude/ directory is on sys.path), not from the workspace root. Script invocations like python .claude/skills/.../script.py can be run from the workspace root because those scripts manage their own path setup.

Steps

Step 0: Preflight Validation

Validate arguments using helpers.command_validation.validate_command_args("callgraph", {"module": "<module>"}). If validation fails, report the errors and stop. On success, use result.resolved["db_path"] for subsequent script calls.

1. Find the module DB

Use the decompiled-code-extractor skill (find_module_db.py) to resolve the module name to its DB path.

Tip: All skill scripts support --json for machine-readable output. Use --json when parsing script output programmatically.

Read the full file on GitHub · 141 lines

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 · 141 lines · 0 tokens per session scan A 5ebcbcf8601c

Subscribe to this mod's changes

callgraph is a command published in the GitHub repository marcosd4h/DeepExtractRuntime (20 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,393 tokens. 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.