> So far, it appears to me that the only thing that makes sense is to have few hooks and scripts that mitigate the stupid token consumption like using code indexers instead of grep
Do you have any specific recommendations for this? Is it providing lists of code-related files or is there something more in depth?
Instead of telling llm the full command line to do the tests, add a script run_tests.sh, same for linting or whatever. Output errors to a file and only output the filename when there are errors to check.
Add a hook of your preference to run those items when task is over.
To be honest, I also have a skill for Claude for that but not because Claude needs it but so it avoid trying to figuring out how to run.
On claude.md I instruct it to leave the execution to the hooks instead (unless debugging)
I use rtk and caveman when in the mood but mostly to remove the obnoxious verbosity of Claude. I tested both for weeks and they didn't really saved that much money for Opus model.
I have zero base to prove but reading the thinking output, when you set the effort to high or more, it start repeating stuff over and over...
Opus 4.7 seems geared towards taking the most money possible.
Tasks that opus 4.6 and sonnet 4.6 did in X tokens, opus will take 2X to 3X and the final cold isn't much better.
Do you have any specific recommendations for this? Is it providing lists of code-related files or is there something more in depth?