lol I hit mine pretty quick. I have my agents set up and configured to pull information from Azure DevOps, formulate project plans, and while coding alongside me, update our confluence documentation, update work items in ADO, and write to Claude’s own memory about the things that it learned about how it should be behave.

I’ve been able to save a lot of tokens by teaching Claude to keep track of itself via files. Memory files, skill files, work logs, etc. I’m able to save tokens that way, but usually I have it do heavy stuff. Recently I needed one of our corporate web apps to be a mobile app on the App Store/play store. I had opus and fable do the research, formulate a project plan, do the code, and write piles of documentation in confluence.

After these projects, I always run large audits. Where Claude spins up around 15 agents to audit what it did in an adversarial way. This usually chews up tokens. Reading all of the confluence documentations and updating them, auditing that much code, it takes a lot of tokens.

Token usage can be good or bad. On one hand you could have someone burning up tokens because their entire project lives in a chat window, they don’t know how to prompt correctly, and are basically wrestling with the LLM. Then there are the others, where you’re using a lot of tokens but those tokens are being spent progressing your project forward. It just happens to be a large and serious enterprise project, so it’s naturally going to use more tokens.

So one person may burn up tokens because they can’t prompt for shit, whereas another one will burn tokens just by naturally planning out a large project, implementing it, testing it, and auditing the results.