That is a lot of ways to spend a budget, and nobody can afford all of them on everything. So the last question is where the next token goes.
Verification spend
Also called Verification budget, Where the tokens go
Choosing where a limited budget of tokens and attention goes: mechanical gates, running the real thing, formal checks, or a model reading the code. Each sees things the others can't, so ask what this change could get wrong, and which check could see that.
An agent will spend on whichever check you ask for, and each one reports success in the same tone. Good practitioners disagree about where the money should go, and the evidence is thin. So the skill isn't knowing the right mix. It is being able to say what you bought, and what you still can't see.
Say it to your agent
“Before you spend anything on this change, list the ways it could be wrong. For each one, say which check could see it: types or lint, a test, a real run, a model check, or a read-through. Spend only on checks that could see something, and name any risk nothing here can see.”