---
title: "Comment by Ahmet Özel on \"Does Claude prompt caching save money? The break-even math\" | Hashnode"
description: "The 33 usage blocks matching your own engine is a useful consistency check. I would add a few independently hand-calculated fixtures too, especially one request"
url: "https://hashnode.com/posts/does-claude-prompt-caching-save-money-the-break-even-math/6afb35210eb6ca71dd1eae50/comment/6afb752391b1c666ea4e31f4"
---

[Discussion](https://hashnode.com/posts/does-claude-prompt-caching-save-money-the-break-even-math/6afb35210eb6ca71dd1eae50)

Comment [Does Claude prompt caching save money? The break-even math](https://hashnode.com/posts/does-claude-prompt-caching-save-money-the-break-even-math/6afb35210eb6ca71dd1eae50)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[4d ago](https://hashnode.com/posts/does-claude-prompt-caching-save-money-the-break-even-math/6afb35210eb6ca71dd1eae50/comment/6afb752391b1c666ea4e31f4)

The 33 usage blocks matching your own engine is a useful consistency check. I would add a few independently hand-calculated fixtures too, especially one request containing both five-minute and one-hour writes, plus a read followed by an ordinary uncached suffix.

The max(0, writes - w1h) line also deserves an input-consistency check. If hourly writes exceed total writes, silently clamping the remainder hides malformed telemetry. Recording that case as unresolved would keep the savings report auditable when log formats or provider usage fields change.

[NeverPayTwice](https://hashnode.com/@neverpaytwice)

[4d ago](https://hashnode.com/posts/does-claude-prompt-caching-save-money-the-break-even-math/6afb35210eb6ca71dd1eae50/comment/6afb752391b1c666ea4e31f4#reply-6afb9acb83359ea66c8f00c1)

Thanks, both fair points, and both are done as of today. The script now leaves a line out of the totals and reports it as inconsistent when the one-hour writes exceed total writes, or when the five-minute and one-hour split doesn't add up to the total, instead of clamping it. There's also a tests file with hand-calculated cases: a request with both write types, a cache read followed by an uncached suffix, and the two malformed breakdowns. The costs function quoted in the post is unchanged; the check runs before it.
