A code graph tool we tried on a small repo measured net-negative and got removed — more cost than it returned on a codebase that size, so the graph came out of the stack entirely. Agentic coding putting review on finished work is the right split, and the same cost bar applies one layer down to everything feeding the agent: graph, planner, check runner. When a tool loses that measurement, yank it; otherwise the finished-work review just inherits a slower, heavier path to the same full read-through on every task you hand over.