topos

We're trying to up the GPA on the code quality exam by giving them access to structural metrics calculated on graph representations of the programs they write. Hoping this is the study guide template they need to start getting an A in minimizing slop, even if they're actually a D student. They're good at optimizing against scores... https://github.com/Krv-Labs/topos

Refactoring code with Topos cleans up your program structure. Agents optimize for simpler ASTs and lower coupling scores via MCP. We ran a controlled experiment: implement 4 features into two identically-functioning repos -- one that had been refactored using Topos and one that has not been -- using Gemini-CLI w/ gemini-3.1-pro-preview. Findings: - 32.6% fewer tokens to add features to the Topos-optimized repo - 22.9% faster - 24.6% cheaper Measures, concepts, and details of the experiment are provided in the Topos docs. Docs: https://docs.krv.ai/topos/ Github: https://github.com/Krv-Labs/topos

Code review is the new bottleneck. "Tests passing" is no longer sufficient to trust the changes, and the (human) cost of evaluating the quality and robustness of new agent-written contributions is skyrocketing. We built Topos to evaluate code quality based on the structural properties of the programs themselves. We map your files to graphs (AST, CFG, CPG, MDG) and calculate metrics that can characterize how simple, composable, or secure your programs are. Agents can use this tool as they write and optimize based on your preferences. And yes, the inspiration for the repository is from category theory: this is inspired by a topos for program evaluation, that comes equipped with objects (program representations), morphisms (maps on graphs), probes, profunctors, test-coverage metrics, and a custom subobject classifier (Heyting algebra generat