graph-refresh

A command for rebuilding a searchable map of Python code so code-relationship queries reflect the files currently on disk.

In plain words
What is it for?
Use it after structural edits to the specified Python packages, then rerun code-graph queries to inspect the updated results.
Why use it?
A code graph is a snapshot made when the code was last indexed, so later structural changes can be missing. Refreshing it updates relationships such as functions, classes, imports, decorators, renames, and moved files.

Command for Claude Code

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 commands/cognitx-leyton/codegraph/graph-refresh
Clone the repo
git clone --depth 1 https://github.com/cognitx-leyton/codegraph

Made for: Claude Code.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 414 The whole file, excluding the scripts and references it only reads on demand.
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.00018 $0.00414
Opus 5 $0.00009 $0.00207
Sonnet 5 $0.00004 $0.00083
Haiku 4.5 $0.00002 $0.00041

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

Security

Grade A, and why

graph-refresh 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 yesterday.

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/commands/graph-refresh.md · 38 lines

What it actually says

Why

codegraph is a static snapshot of the codebase at index time. Edits after indexing don't show up in the graph until you re-index. Run this command after any structural change — adding/removing classes, functions, methods, imports, decorators; renaming; moving files. For cosmetic edits (comment changes, reformatting), it's not necessary.

What this does

Re-parses every .py file under codegraph/codegraph/ and codegraph/tests/ and upserts nodes / edges into Neo4j. Does not wipe the rest of the graph — Twenty (or any other indexed TS repos) stays untouched. Typical runtime: ~5 seconds for both packages.

codegraph index \
    /home/edouard-gouilliard/Obsidian/SecondBrain/Personal/projects/graphrag-code \
    -p codegraph/codegraph \
    -p codegraph/tests \
    --no-wipe \
    --skip-ownership

--no-wipe keeps other graphs alive. --skip-ownership skips the git-log pass (faster; owners can be added back later if needed).

After running

Re-run any /graph queries you had open — results should reflect the latest code. If something unexpected disappeared, it's more likely a parser edge case than a data loss: check the AST of the file in question, or open an issue.

Indexing a different repo

To point the graph at some other TS / Python repo:

codegraph index /path/to/repo -p <package>

Drop --no-wipe if you want to start from a clean graph (wipes everything, including the codegraph + Twenty snapshots).

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. yesterday First seen · 38 lines · 18 tokens per session scan A c67620d1aa4b

Subscribe to this mod's changes

graph-refresh is a command published in the GitHub repository cognitx-leyton/codegraph (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 414 once invoked, about $0.0001 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.