ontomics
ontomics gives any coding agent instant knowledge of your codebase. One tool call instead of 19. ~20x fewer tokens.
https://github.com/user-attachments/assets/01afa8a0-1bc2-4686-94d7-965fef7610c3
Visualization for the voxelmorph project -- a library for unsupervised learning in image registration
Benchmark
Tested with Claude Sonnet — same question, with and without ontomics.
"What does 'transform' mean in this codebase?" on voxelmorph (full transcript):
| With ontomics | Without | |
|---|---|---|
| Tool calls | 1 | 19 |
| Tokens | ~3.7k | ~76k |
| Time | 5s | 1m 15s |
| Answer quality | Complete | Complete |
"What are the main domain concepts in this codebase?" on ScribblePrompt (full transcript):
| With ontomics | Without | |
|---|---|---|
| Tool calls | 1 | 26 |
| Tokens | ~3.7k | ~61.6k |
| Time | ~5s | 56s |
| Answer quality | Complete | Complete |
Both conditions produced complete, correct answers. ontomics got there in one call.
What it does that search can't
Search tells you where a string appears. An LSP tells you where a symbol is defined and referenced. Neither answers: what are the domain concepts in this codebase? How do they relate? What naming conventions emerged? What changed in the domain vocabulary since last release? Which functions behave similarly, regardless of what they're named?
