Claude Code built a machine to explain prompt caching

4 hours ago

I asked Claude Code to explain prompt caching. It built me this machine.

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00Claude Code built this to explain prompt caching
  2. 0:05One line, with a free skill called Anatomy
  3. 0:09First call: it reads every tile. $0.104
  4. 0:18Cached: $0.008 a call
  5. 0:25The catch: the cache lasts 5 minutes
  6. 0:3322 minutes. One prompt.
  7. 0:40npx skills add wheresryan22/anatomy
  8. 0:48What would you have it explain?
Show transcript

Claude Code built this to explain prompt caching

I asked Claude Code to explain prompt caching. It built me this machine.

One line, with a free skill called Anatomy

One line, and a free skill called Anatomy.

First call: it reads every tile. $0.104

Each tile is a thousand tokens of the prompt. The first call reads every one, and pays a little extra to cache them: about ten cents.

Cached: $0.008 a call

Call again, and the clamped tiles are already cached. The reader skips them, and the call costs less than a cent.

The catch: the cache lasts 5 minutes

The catch: the cache only lasts five minutes. Wait any longer, the clamps let go, and the next call pays to read it all again.

22 minutes. One prompt.

Our run, 14 October

About 70 parts, on Opus 5.5. It checked every line of its own drawing before it stopped.

It took twenty-two minutes on its own. And it checked every line of its own drawing before it stopped.

npx skills add wheresryan22/anatomy

Free · MIT · Claude Code, Codex, OpenCode

About 9,900 GitHub stars in six days.

github.com/wheresryan22/anatomy ↗

Anatomy is free, and it runs in Codex and OpenCode too. It's at almost ten thousand GitHub stars in under a week.

What would you have it explain?

Your turn

What would you have it explain? Tell me below.