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 agentmods add commands/cognitx-leyton/codegraph/graphgit clone --depth 1 https://github.com/cognitx-leyton/codegraphWhat 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 | $0.00016 | $0.00703 |
| Opus 5 | $0.00008 | $0.00351 |
| Sonnet 5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
graph 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage
/graph <cypher>
Runs the Cypher against the local Neo4j instance via codegraph query --json. Read-only — writes (CREATE, MERGE, DELETE, SET) are not rejected at the CLI level (unlike the MCP server), so be careful what you execute. If you're unsure, stick to MATCH queries.
Assumes:
- Neo4j is up at
bolt://localhost:7688(docker compose up -dfromcodegraph/if not). - The graph has been indexed at least once (run
/graph-refreshif you get zero results on queries you expect to match).
Canonical query patterns for this repo
~20 files, 56 classes, 134 module functions, ~180 methods
Blast radius — who depends on a file?
MATCH (f:File)-[:IMPORTS]->(target:File {path: 'codegraph/codegraph/schema.py'})
RETURN f.path AS caller
ORDER BY f.path
Who imports a specific symbol?
MATCH (f:File)-[r:IMPORTS_SYMBOL]->(g:File)
WHERE r.symbol = 'IgnoreFilter'
RETURN f.path AS caller, g.path AS source
Find a class by substring
MATCH (c:Class)
WHERE c.name CONTAINS 'Node' AND c.file STARTS WITH 'codegraph/codegraph/'
RETURN c.name, c.file
ORDER BY c.name
Methods on a class
MATCH (c:Class {name: 'IgnoreFilter'})-[:HAS_METHOD]->(m:Method)
RETURN m.name, m.visibility, m.is_constructor
ORDER BY m.name
Census of dataclasses
MATCH (f:File)-[:DEFINES_CLASS]->(c:Class)-[:DECORATED_BY]->(d:Decorator {name: 'dataclass'})
WHERE f.path STARTS WITH 'codegraph/codegraph/'
RETURN f.path, count(c) AS dataclass_count
ORDER BY dataclass_count DESC
What decorators does a file use?
MATCH (:File {path: 'codegraph/codegraph/mcp.py'})-[:DEFINES_FUNC]->(fn:Function)-[:DECORATED_BY]->(d:Decorator)
RETURN fn.name, d.name
ORDER BY fn.name
Unresolved (external) imports from a file
MATCH (:File {path: 'codegraph/codegraph/cli.py'})-[r:IMPORTS {external: true}]->(e:External)
RETURN e.specifier
ORDER BY e.specifier
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.
- 2d ago First seen · 91 lines · 16 tokens per session scan A c5336995e375
graph is a command published in the GitHub repository cognitx-leyton/codegraph (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 703 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.
Other commands, from other repositories
feedback
Security Design Review — PRD/기획서 기반 보안 의견서·검토 의견서 생성.
compliance
이전 보안 진단 보고서의 Finding들이 패치되었는지 확인하고, 변경된 코드에서 신규 취약점을 탐색합니다.
va
Vulnerability Assessment — 8차원 아키텍처 진단 + Self-Verify + Evidence Verification.
pentest
Penetration Testing — 시나리오 기반 모의해킹 + POC + 라이브 검증 (State Delta 기반).
redteam
Red Team Operations — 인프라 설정 보안 리뷰 + MITRE ATT&CK + Detection Engineering.
verify
Adversarial Verification — 보안 진단 보고서 독립 검증 (Autonomous First).