code-explorer

code-explorer is an agent for Claude Code from sdsrss/code-graph-mcp. It costs 28 tokens per session (572 once invoked), scanned A, original, MIT.

A code-understanding agent that maps how parts of a software project connect, using the program’s structure and relationships. An AST is a structured representation of source code that helps it inspect symbols and calls.

In plain words
What is it for?
Use it to map a repository, trace an API or function call chain, inspect symbols and their callers, find references before renaming or removing code, and search code by meaning.
Why use it?
It helps when a project is unfamiliar or when a change may affect code in many places. Relationship-based searches can show where functions are defined, called, or referenced.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions Claude Code.

Part of the code-graph-mcp plugin — 2 skills, 1 agent, 6 hooks, 1 MCP server shipped together

Good fit Use it to map a repository, trace an API or function call chain, inspect symbols and their callers, find references before renaming or removing code, and search code by meaning.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/sdsrss/code-graph-mcp/code-explorer
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.

Clone the repo
git clone --depth 1 https://github.com/sdsrss/code-graph-mcp

Made for: Claude Code.

Or install code-graph-mcp, the plugin that ships this one along with the rest of its 2 skills, 1 agent, 6 hooks, 1 MCP server.

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-explorer

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/sdsrss/code-graph-mcp/code-explorer"><img src="https://agentmods.dev/badge/agents/sdsrss/code-graph-mcp/code-explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 572 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.00028 $0.00572
Opus 5.5 $0.00011 $0.00229
Sonnet 5.5 $0.00006 $0.00114
Haiku 4.5 $0.00003 $0.00057

Measured 16d ago against content hash 6b3edb0b31e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-explorer 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 16d 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.

claude-plugin/agents/code-explorer.md · 30 lines

What it actually says

You are a code exploration specialist with access to an AST knowledge graph.

Strategy

The CLI answers from Bash with no tool loading; the MCP tools return the same data.

  1. Map first: code-graph-mcp overview <dir> (MCP module_overview) or code-graph-mcp map --compact (project_map) for an unfamiliar area.
  2. Locate: code-graph-mcp show X for a named symbol; code-graph-mcp search "words" or MCP semantic_code_search when you only know what the code does.
  3. Relate: code-graph-mcp callgraph X (get_call_graph; route_path='GET /api/x' traces an HTTP handler) and code-graph-mcp impact X (get_ast_node include_impact=true).
  4. Audit uses: code-graph-mcp refs X (find_references), then grep for what the graph cannot see; ast_search enumerates symbols by type / return / params.
  5. Read the files the answer points to; use Grep for literal strings and non-code files.

Rules

  • Calls through dynamic dispatch, reflection or unresolved imports are not in the graph: an empty caller list is not proof of no callers.
  • Return structured findings: name, file, line, relationships.
  • When reporting call chains, include depth and direction.
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. 16d ago Changed · +3 lines 6b3edb0b31e0
  2. 1mo ago Changed · +3 lines cd5f204a7a80
  3. 1mo ago First seen · 24 lines · 28 tokens per session scan A 86ea5d66583e

Subscribe to this mod's changes

code-explorer is an agent published in the GitHub repository sdsrss/code-graph-mcp (84 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 572 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other agents, from other repositories

rust-async-safety-reviewer

Reviews Rust async code for tokio + libsql + axum concurrency hazards. Use after changes touching tokio::spawn, axum handlers, libsql connection usage, or any Send/Sync boundaries. Read-only — produces findings, does not edit.

wenlan-app/wenlan · 59 tokens

codeweb-dissector

Read-only atomic dissection pass for the codeweb plugin. Given a file set or subsystem and an engine mode, extracts atomic nodes (functions, classes, methods, exported symbols) and their relationship edges (calls, imports, inheritance) as JSON conforming to the codeweb graph schema. Used in parallel fan-out passes.…

GhostlyGawd/codeweb · 76 tokens

codeweb-domain-mapper

Read-only domain-tagging and overlap-detection pass for the codeweb plugin. Given the merged node/edge graph, clusters nodes into semantic domains, assigns a domain to every node, and detects cross-domain overlap (duplicated logic, parallel implementations, tangled responsibilities) with ranked consolidation…

GhostlyGawd/codeweb · 67 tokens

tp-dead-code-finder

Use this when the user asks to find or remove dead / unused code ("clean up this file", "find unused exports", "pre-release cleanup"). Picks the fastest per-language analyzer first (go vet/deadcode, phpstan, vulture, ts-prune), falls back to findunused + findusages cross-check. Output-only — NEVER deletes code itself.

Digital-Threads/token-pilot · 81 tokens

tp-debugger

PROACTIVELY use this when the user reports a bug, stack trace, error message, failing behaviour, or asks "why does X break / fail / throw". Traces root cause via call-tree without reading whole files first. Do NOT use for writing new features or planning changes.

Digital-Threads/token-pilot · 62 tokens

tp-incident-timeline

PROACTIVELY use this when the user reports a production incident and asks "what changed before this", "what was deployed in the window", "correlate the bug with recent commits". Builds a timeline of commits / diffs / touched-symbols bounded by the incident time-window, then ranks by suspected correlation.

Digital-Threads/token-pilot · 70 tokens