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.
npx skills add sdsrss/code-graph-mcp --skill exploregit clone --depth 1 https://github.com/sdsrss/code-graph-mcpWrote 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.
[](https://agentmods.dev/skills/sdsrss/code-graph-mcp/explore)<a href="https://agentmods.dev/skills/sdsrss/code-graph-mcp/explore"><img src="https://agentmods.dev/badge/skills/sdsrss/code-graph-mcp/explore/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.
<a href="https://agentmods.dev/skills/sdsrss/code-graph-mcp/explore"><img src="https://agentmods.dev/badge/skills/sdsrss/code-graph-mcp/explore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00055 | $0.00285 |
| Opus 5.5 | $0.00022 | $0.00114 |
| Sonnet 5.5 | $0.00011 | $0.00057 |
| Haiku 4.5 | $0.00006 | $0.00028 |
Grade A, and why
explore 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.
What it actually says
Explore Code (indexed project)
Use these BEFORE reading individual files:
| Need | Command | Replaces |
|---|---|---|
| Module structure | code-graph-mcp overview <dir> |
5+ Read calls |
| Project architecture | code-graph-mcp map --compact |
ls + README |
| Who calls / what calls | code-graph-mcp callgraph <symbol> |
Grep + manual trace |
| Find by concept | code-graph-mcp search "concept" (full-text) |
3+ Grep attempts |
| Impact before a signature change | code-graph-mcp impact <symbol> |
Grep for callers |
| Every use (rename / remove) | code-graph-mcp refs <symbol>, then grep -w |
Grep alone |
Workflow: overview first → Read only the file you will edit. Calls the graph could not resolve (dynamic dispatch, reflection, unresolved imports) are not in it, so confirm an empty answer with grep.
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.
- 16d ago Changed · +3 lines · -2 tokens per session b876bdfecd2f
- 1mo ago First seen · 23 lines · 57 tokens per session scan A 52dc7e92976c
explore is a skill published in the GitHub repository sdsrss/code-graph-mcp (84 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 285 once invoked, about $0.0002 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-09-14.
Other skills, from other repositories
why
Work out whether a failure is your machine or your code before debugging either, using the environment this repository has declared and the dependency map. Use when a test, build or command fails and the cause is not obvious from the error.
frigg-first-code-search
Default to Frigg MCP instead of shell rg/grep/find/fd/cat/sed for source-code discovery, search, navigation, and proof reads in attached repos. Scenario-first routing: pick the flow, then the tool. Shell remains correct for git, build/test output, generated/unindexed paths, explicit live-disk checks, and when Frigg is…
dekko-verify
Sanity-check a suspiciously low or zero call-graph result from dekko (getcallers, getcallees, findusages, impactedtests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to…
dekko-refactor
List every site a rename, move, or signature change must touch before editing, then prove nothing was missed after. Trigger when about to rename a function, method, class or type, rename or move a file or module, change a parameter list or return type, move a symbol between files, or remove a symbol, in a repo with a…
dekko-debug
Work a stack trace, exception, or error report from dekko's map instead of reading each frame's file. Trigger when given a traceback, an exception type or message, a failing test's error, or a question like "why does X raise", "who handles this error", "how does control get from A to B", or "where is this env var…
gossiphs
Use when you need to find related files, understand code dependencies, or analyze impact scope. Triggers when the user asks about: "Which files use this function/class?" "What files will be affected if I change this?" "Find code related to X" "What does this file depend on?" "Where is this symbol defined/referenced?"…