Borrowing it
Nothing to install: this file belongs to cognitx-leyton/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.
curl -O https://raw.githubusercontent.com/cognitx-leyton/codegraph/main/.claude/commands/graph-refresh.mdgit clone --depth 1 https://github.com/cognitx-leyton/codegraphWrote 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/commands/cognitx-leyton/codegraph/graph-refresh)<a href="https://agentmods.dev/commands/cognitx-leyton/codegraph/graph-refresh"><img src="https://agentmods.dev/badge/commands/cognitx-leyton/codegraph/graph-refresh/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/commands/cognitx-leyton/codegraph/graph-refresh"><img src="https://agentmods.dev/badge/commands/cognitx-leyton/codegraph/graph-refresh.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.00018 | $0.00414 |
| Opus 5.5 | $0.00007 | $0.00166 |
| Sonnet 5.5 | $0.00004 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00041 |
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 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.
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).
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 · 38 lines · 18 tokens per session scan A c67620d1aa4b
graph-refresh is a command published in the GitHub repository cognitx-leyton/codegraph (12 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 414 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.
Other commands, from other repositories
grasp-build-graph
Run graspanalyze + graspminimalcontext for the current repo, store the sessionid, and report a 100-token orientation.
feedback
A design-stage security review for product requirement documents and other planning documents; a PRD is a document describing what a product should do.
va
A read-only security review of a codebase across eight architecture areas, with findings checked against file-and-line evidence.
compliance
A follow-up security check that verifies whether earlier findings were fixed and, depending on the selected mode, looks for new problems.
pentest
A read-only penetration-testing command for examining source code from an attacker’s perspective and producing proof-of-concept checks. Penetration testing is authorized security testing that tries to verify exploitable weaknesses.
run
A security-workflow coordinator that turns a natural-language request into a plan involving code review, verification, attack testing, or reporting.