I think this would be super useful as a claude code / visual studio extension, so I can see the cost impact of changes I am making in code. For example by adding a prompt pre-processing function how much am I actually going to save in LLM token cost.
Retry logic modeling is a great inclusion most cost estimates miss this completely. In my experience retries account for 15-25% of total cost in production agent systems, especially with tool calling where validation failures trigger re-prompts. Would be useful to see a "worst case" scenario that models cascading retries (retry triggers another tool call that also retries).
2 comments