agentmods.dev

code-graph

code-graph is a skill for Claude Code from NicoV7/codebase-visualizer. It costs 0 tokens per session (717 once invoked), scanned A, original, MIT.

A skill for answering structural questions about a codebase by using a code graph, which maps files, functions, classes, imports, and calls. It can also show architecture and changes in a pull request, a proposed code change for review.

In plain words
What is it for?
Use it to find what calls a function, what a function calls, visualize a project, inspect pull-request impact, or query relationships between code elements.
Why use it?
It avoids unreliable text searches for questions about how code connects. It helps trace dependencies, understand architecture, and estimate which code may be affected by a change.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

not rated 0repo 2mo ago A scan 0 tokens original MIT

Good fit Use it to find what calls a function, what a function calls, visualize a project, inspect pull-request impact, or query relationships between code elements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nicov7/codebase-visualizer/code-graph
View source ↗ NicoV7/codebase-visualizer
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.

Any agent
npx skills add NicoV7/codebase-visualizer --skill code-graph
Clone the repo
git clone --depth 1 https://github.com/NicoV7/codebase-visualizer

Made for: Claude Code.

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

agentmods badge for code-graph

README.md
[![agentmods](https://agentmods.dev/badge/skills/nicov7/codebase-visualizer/code-graph/github.svg)](https://agentmods.dev/skills/nicov7/codebase-visualizer/code-graph)
Your own site
<a href="https://agentmods.dev/skills/nicov7/codebase-visualizer/code-graph"><img src="https://agentmods.dev/badge/skills/nicov7/codebase-visualizer/code-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.

agentmods 80×15 button for code-graph

Your own site · 80×15
<a href="https://agentmods.dev/skills/nicov7/codebase-visualizer/code-graph"><img src="https://agentmods.dev/badge/skills/nicov7/codebase-visualizer/code-graph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 717 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00717
Opus 5.5 $0.00000 $0.00287
Sonnet 5.5 $0.00000 $0.00143
Haiku 4.5 $0.00000 $0.00072

Measured 1mo ago against content hash 73b6cb92fd33, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-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 1mo 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.

skills/code-graph/SKILL.md · 43 lines

How it starts

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

code-graph

Use the code-graph MCP tools (or the codegraph CLI) instead of grepping when the question is structural.

Steps

  1. Not indexed yet? Run index_repo (CLI: codegraph index) once; re-run with incremental=true after changes.
  2. "Who calls X / what does X call" → trace_path(function_name, direction=in|out|both).
  3. "Show the architecture / visualize the codebase" → get_architecture, or codegraph ui for the interactive 3D code city — click a component to expand its files in place, click a file for its functions; --base main adds PR diff badges; --flat gives the 2D no-WebGL map. Share exact views via the hash: #inside=a,b&file=comp:path&trace=N&focus=symbolId.
  4. "What changed in this PR and what does it touch" → diff_overlay(base): per-symbol added/removed line numbers plus hunks; combine with inbound trace_path on changed symbols for blast radius.
  5. Arbitrary structure questions → query_graph with Cypher (nodes: Function, Class, File, Module; edges: CALLS, IMPORTS, CONTAINS).

Descriptions and reasons

  • Before explaining a component, check describe_component(symbol_id); write missing ones with set_description following describe-style.md in this directory. Use list_undescribed to drive a describe-the-codebase loop.
  • When you add, change, or explain non-obvious code, log the why: record_reason(symbol_id, why, kind=exists|changed). Read history with why_trace.

After you build anything (the comprehension contract)

The engineer must come out understanding what you built. For every new or changed symbol:

  1. set_description(symbol_id, ...) per describe-style.md — what it does, in their words not yours.
  2. record_reason(symbol_id, why, kind="changed") — the non-obvious WHY that the code cannot say.
  3. Tell them: run codegraph review --base <ref> — a guided walkthrough of what you built, stop by stop, with a persistent understanding ledger and a comprehension heatmap on the city.
  4. Alternatively run the tour conversationally: build_walkthrough(base) → present each stop's WHAT/WHY/code → mark_understood(symbol_id) only after they confirm. Check get_comprehension() to see what they still have not reviewed — and say so.

Read the full file on GitHub · 43 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago First seen · 43 lines · 0 tokens per session scan A 73b6cb92fd33

Subscribe to this mod's changes

code-graph is a skill published in the GitHub repository NicoV7/codebase-visualizer (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 717 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-31.

Debuggingskills
Related

Other skills, from other repositories

gke-workload-scaling-troubleshooting

Diagnoses GKE HorizontalPodAutoscaler (HPA) failures — metrics showing as , FailedGetResourceMetric / FailedGetScale / FailedComputeMetricsReplicas events, missing Pod resource requests, custom/external metrics-pipeline breakage (FailedGetExternalMetric / FailedGetCustomMetric, unavailable metrics adapter…

google/skills · 170 tokens

gke-ai-troubleshooting-tpu-performance-degradation

Diagnose GKE Cloud TPU training throughput drops and step-time regressions (15%+ TPU duty-cycle drop) using ML Diagnostics Workload Monitoring (gcloud alpha mldiagnostics monitored-events / hypercomputecluster.googleapis.com/v1alpha) and 1-minute Cloud Monitoring system metrics (kubernetes.io/node/accelerator/).…

google/skills · 200 tokens

gke-ai-troubleshooting-jobset-interruption

Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…

google/skills · 83 tokens

gke-node-notready

Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…

google/skills · 112 tokens

bigquery-troubleshooting

Provides diagnostic workflows and step-by-step root-cause analysis procedures for actively broken, failing, or slow BigQuery jobs, execution graph and query plan stage bottlenecks, system performance issues, or unexpectedly expensive workloads. Use when interpreting symptoms, isolating bottlenecks, diagnosing cost…

google/skills · 140 tokens

gke-ai-troubleshooting-tpu-vbar-oom

Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…

google/skills · 125 tokens