codegraph CLAUDE.md

Developer instructions for codegraph, a Python tool that maps TypeScript and Python code into a Neo4j graph database.

In plain words
What is it for?
They guide indexing, querying, validating, and wiping the graph, plus using its command line, interactive Cypher shell, and read-only MCP server.
Why use it?
They explain how to use the code graph during development to find relationships and problems that ordinary language tools may miss.

Instructions file

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 instructions/cognitx-leyton/codegraph/claude-md
Clone the repo
git clone --depth 1 https://github.com/cognitx-leyton/codegraph
Per session 2,607 This file is loaded in full into every session.
When invoked 2,607 The same file — it is already loaded in full.
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.02607 $0.02607
Opus 5 $0.01303 $0.01303
Sonnet 5 $0.00521 $0.00521
Haiku 4.5 $0.00261 $0.00261

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

Security

Grade A, and why

codegraph CLAUDE.md 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.

CLAUDE.md · 130 lines

How it starts

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

CLAUDE.md

Guidance for Claude Code (and similar coding agents) working on this repo.

Project summary

codegraph (package: codegraph) is a Python tool that indexes TypeScript and Python codebases into a Neo4j property graph. It walks source with tree-sitter, recognises framework constructs (NestJS controllers / injectables / modules, React components and hooks, TypeORM entities, GraphQL operations, Python classes and decorators), and loads typed nodes + edges into Neo4j. Downstream consumers:

  • CLI: codegraph index, codegraph query, codegraph validate, codegraph wipe — Typer app.
  • MCP server: codegraph-mcp stdio server with 16 read-only tools. Optional extra (pip install "codegraph[mcp]").
  • REPL: interactive Cypher shell at codegraph repl.

This repo is itself Python, and codegraph parses Python since Stage 1 shipped. So we can dogfood: Claude Code can query the graph of codegraph-the-codebase while implementing codegraph-the-tool.

Using the graph during development

Two slash commands wire the local Neo4j graph into your Claude Code workflow. Use them — they exist to catch mistakes the language server can't.

/graph <cypher> — query the live graph

Read-only Cypher against bolt://localhost:7688. Prefer this over manual codegraph query in Bash because the slash command has the permissions pre-approved and a body of canonical query patterns. See .claude/commands/graph.md for examples.

When to run /graph:

  • Before renaming a class, function, or file → check blast radius with MATCH (f:File)-[r:IMPORTS_SYMBOL]->(g:File) WHERE r.symbol = 'X' RETURN f.path, g.path.
  • Before deleting a function or method → confirm nothing depends on it.
  • Before moving a module → count incoming IMPORTS edges; you'll need to update every caller.
  • When asked "who calls X?" or "where is Y used?" — almost always a one-query answer.
  • When in doubt about what exists/graph "MATCH (c:Class) WHERE c.name CONTAINS 'Foo' RETURN c.name, c.file" is faster and more exhaustive than grep.

Read the full file on GitHub · 130 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 · 130 lines · 2,607 tokens per session scan A cba197e193ac

Subscribe to this mod's changes

codegraph CLAUDE.md is an instructions file published in the GitHub repository cognitx-leyton/codegraph (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,607 tokens to every session, about $0.0130 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.