What is codegraph CLAUDE.md?

Repository instructions for codegraph, a tool that turns TypeScript, JavaScript, or Vue source code into a graph of files and relationships. The graph is saved as one JSON file, then shown in a web viewer or read by an AI server.

Understanding the repository layout, extracting a code graph, running the viewer or MCP server, and verifying changes with tests.

They explain how the extractor, viewer, and AI server fit together so changes keep their shared data format working.

How RexHung0302/codegraph configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to RexHung0302/codegraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/RexHung0302/codegraph/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/RexHung0302/codegraph

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/rexhung0302/codegraph/claude-md/github.svg)](https://agentmods.dev/instructions/rexhung0302/codegraph/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/rexhung0302/codegraph/claude-md"><img src="https://agentmods.dev/badge/instructions/rexhung0302/codegraph/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/rexhung0302/codegraph/claude-md"><img src="https://agentmods.dev/badge/instructions/rexhung0302/codegraph/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 987 This file is loaded in full into every session.

When invoked 987 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00987	$0.00987
Opus 5.5	$0.00395	$0.00395
Sonnet 5.5	$0.00197	$0.00197
Haiku 4.5	$0.00099	$0.00099

Measured 2mo ago against content hash e46316b5f485, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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 · 55 lines

How it starts

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

CLAUDE.md

Guidance for Claude Code when working in this repository.

What this is

codegraph extracts a TS/JS/Vue repo into a node/edge graph (graph.json), then serves it two ways: a WebGL viewer for humans, an MCP server for agents. There is no database and no backend — the graph is one JSON file passed between three independent pieces.

Layout

Path	Role
`src/extract.ts`	CLI extractor. ts-morph AST walk → `graph.json`. The only place that knows about source languages.
`src/mcp.ts`	MCP server over stdio. Reads `graph.json`, never parses source.
`web/src/main.ts`	Viewer. graphology + sigma + ForceAtlas2 worker.
`web/public/graph.json`	Default extractor output. Git-ignored — regenerate, never commit.
`docs/graph-schema.md`	The contract between the three pieces. Update it when the shape changes.
`tests/`	vitest suite; `tests/fixtures/` are tiny repos the extractor runs against.

Commands

pnpm extract <repo> [--out f] [--exclude a,b] [--types]   # produce a graph
pnpm dev                                        # viewer on :5173
pnpm mcp [graph.json]                           # MCP server on stdio
pnpm test                                       # vitest, 52 cases
npx tsc --noEmit

There is no linter config. pnpm test and npx tsc --noEmit must both pass before any change is considered done.

tests/fixtures/ holds three miniature repos — a React app with tsconfig paths, a Vue CLI style app with no tsconfig and a pug template, and a types-app whose re-export and same-name method exist only to pin --types behaviour. They exist to pin behaviour that is easy to break silently: alias resolution, SFC parsing, renders edges, edge dedup, determinism. When you change extraction, add a fixture case rather than adjusting an assertion to match new output.

How to verify a change

Type-checking is not enough — extraction bugs type-check fine and silently produce a wrong graph.

Extractor changes: re-run pnpm extract on at least one React repo and one Vue repo (and, when touching resolution, once more with --types: it must only add edges, never remove any), and compare the per-type edge counts printed at the end against the previous run. A change that drops imports or renders to near zero is the classic regression; that is how the alias and Vue bugs were caught.
MCP changes: drive the server with a real MCP client over stdio (@modelcontextprotocol/sdk Client + StdioClientTransport) and call the affected tool. Do not assert from reading the code.
Viewer changes: take a screenshot with Playwright and check the console is error-free. HTTP 200 proves nothing — a WebGL canvas can be blank.

Read the full file on GitHub · 55 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.

2mo ago First seen · 55 lines · 987 tokens per session scan A e46316b5f485

Subscribe to this mod's changes

codegraph CLAUDE.md is an instructions file published in the GitHub repository RexHung0302/codegraph (0 stars, last pushed 3mo ago), licensed MIT. It adds 987 tokens to every session, about $0.0039 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-31.

codegraph CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
codegraph CLAUDE.mdRexHung0302/codegraph	Instructions file	0	3mo ago	MIT	A	987	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

codegraph: Instructions file for Claude Code