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 skills add HelloThisWorld/open-mind --skill code-graphsgit clone --depth 1 https://github.com/HelloThisWorld/open-mindWrote 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/skills/hellothisworld/open-mind/code-graphs)<a href="https://agentmods.dev/skills/hellothisworld/open-mind/code-graphs"><img src="https://agentmods.dev/badge/skills/hellothisworld/open-mind/code-graphs/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/skills/hellothisworld/open-mind/code-graphs"><img src="https://agentmods.dev/badge/skills/hellothisworld/open-mind/code-graphs.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.00047 | $0.00470 |
| Opus 5.5 | $0.00019 | $0.00188 |
| Sonnet 5.5 | $0.00009 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
code-graphs 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 1mo 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
Code graphs — deterministic structure map
What it does
Performs line-oriented static analysis (language specs in openmind.langspec,
tree-sitter for Java where available) to recover, for ANY repository, a persisted
structure artifact: a module tree, a per-file definition index, entry points, an
import/dependency graph, and a name-based call/usage graph. From it, openmind.diagrams
projects interactive call graph data plus Mermaid / DOT diagrams.
Determinism & anti-fabrication contract
- Graphs are recovered from facts in the code (defs, imports, call sites) — never model-generated.
- Internal import edges are resolved where the language makes it tractable; unresolved/external references are recorded as such, never invented.
- Call edges are name-based and flagged
ambiguouswhen a symbol is defined in more than one file — the tool states uncertainty instead of guessing. - File nodes and definitions carry source locations; directory/module nodes are rollups over real files. There is no path that fabricates an edge.
- Incremental: hash-keyed per file, so an unchanged file is not re-scanned.
Invocation
- REST:
GET /structure?scope=(overview: stats, entry points, top modules),GET /graph?scope=(call roots),GET /graph/children, andGET /graph/node?scope=&id=(a node's source location, defs, call neighbors, cross-linked glossary terms). - Library:
openmind.structure.build_structure(...),get_definition(doc, symbol),term_usage(doc, term);openmind.diagramsfor projections.
Implementation / tests
openmind/structure.py, openmind/diagrams.py, openmind/langspec.py,
openmind/javaparse.py. Acceptance: tests/verify_structure.py, tests/verify_diagrams.py.
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.
- 1mo ago First seen · 37 lines · 47 tokens per session scan A a89d4be9875a
code-graphs is a skill published in the GitHub repository HelloThisWorld/open-mind (1 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 470 once invoked, about $0.0002 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.
Other skills, from other repositories
memtrace-first
Route code discovery, debugging, flow tracing, how-code-works questions, and pre-edit rationale checks in indexed source-code repos to Memtrace graph plus Cortex decision tools. Use first before searching/reading code, and before editing, refactoring, deleting, or re-picking an approach that may have a recorded…
memtrace-incident-investigation
Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history. Use when the user asks about root cause analysis, what broke, or what changed when debugging a failure. Do not start with Grep, Glob, rg, find, or…
memtrace-preflight
Run a one-call pre-flight check on a single existing symbol before editing it: blast radius, co-change partners, complexity, 30-day churn, and verification checklist, then check Cortex decision memory for rationale/bans when intent may matter. Use before modifying any existing function or symbol you did not just…
cartograph
Explore a codebase through Cartograph v2's PostgreSQL code graph: intent-aware context, exact/BM25/hybrid search, callers/callees/impact, affected tests, live source, review, freshness, and bounded index administration.
memtrace-cochange
Find files that historically co-change with a target symbol or file, ranked by co-occurrence across git episodes. Use when the user asks about historical coupling, co-change, what changes with this, hidden dependencies, or what else needs to move for source code. Do not use git log, git diff, Grep, or manual file…
memtrace-episode-replay
Replay the graph diff of one episode — a single git commit or working-tree save — to inspect what it changed: added/modified/removed symbols and edges. Use when the user asks what one commit or save changed in the graph, why code looks this way, or wants to inspect implementation attempts, reversions, past reasoning…