Firing off cache writing costs 1.2x tokens iirc. Meaning non repeatable tasks will cost more in the long run.
Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
31–33 of 33 posts
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#32Interesting – I've been using Claude heavily for building projects without writing code myself. Token costs add up fast, anything that reduces that is welcome. Has anyone tested this in production workflows?
I've found RTK CLI proxy [1] quite useful for reducing token usage
Re: Prompt-caching – auto-injects Anthropic cache breakpoints (90% token savings)
#33Earlier quoted context omitted.
Does anyone actually read anymore? From the FAQ: You're right, and it's a fair question. Claude Code does handle prompt caching automatically for its own API calls — system prompts, tool definitions, and conversation history are cached out of the box. You don't need this plugin for that. This plugin is for a different layer: when you build your own apps or agents with the Anthropic SDK. Raw SDK calls don't get automa…
Is this a joke? The first thing on the page is "Automatic prompt caching for Claude Code." Why should one expect this to actually be "Automatic prompt caching for new apps you develop with Claude Code"? It appears to be hard to explain what this plugin does, and the authors did a terrible job; they did not even try.
> Is this a joke?
Yes, your comment is a joke. I agree.