Skip to content
Back to skills

Prompt Cache Kit

ASecurity

Make dynamic agents cheaper by keeping their prompt prefixes byte-identical so the prompt cache hits. Use whenever you are about to spawn subagents, forks, parallel agents or a Workflow, run /loop or ScheduleWakeup, or when the user says "save tokens", "prompt caching", "cache hit", "token usage", "ลด token". Builds a fingerprinted, byte-stable project outline locally with uv (no API key, no LLM), generates agent briefs that put that outline first and the task last, and reports per-agent cach...

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentspythongitapi

Works with

  • claude code
  • api
  • mcp

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add th3r-dev/th3-skills --skill prompt-cache-kit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prompt Cache Kit?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Prompt Cache Kit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/th3r-dev-prompt-cache-kit/badge)](https://www.skillsdirectory.com/skills/th3r-dev-prompt-cache-kit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: prompt-cache-kit
description: Make dynamic agents cheaper by keeping their prompt prefixes byte-identical so the prompt cache hits. Use whenever you are about to spawn subagents, forks, parallel agents or a Workflow, run /loop or ScheduleWakeup, or when the user says "save tokens", "prompt caching", "cache hit", "token usage", "ลด token". Builds a fingerprinted, byte-stable project outline locally with uv (no API key, no LLM), generates agent briefs that put that outline first and the task last, and reports per-agent cache hit rate from the local Claude Code session logs.
---

# Prompt Cache Kit

Claude Code already sends prompt caching on every request. A cache hit needs a **byte-identical prefix**, and a hit costs about 0.1× the normal input price, while a write costs about 1.25× (5m TTL) or 2× (1h TTL). Whether dynamic agents get hits depends on how you write their prompts. This skill keeps those prompts identical where it counts.

Idea borrowed from Understand-Anything: do the structural work locally and deterministically, fingerprint files so only changed ones get recomputed, and let agents read the precomputed result instead of re-reading the repo.

Tool: `uv run --script ${CLAUDE_SKILL_DIR}/scripts/pcache.py <cmd>`. It's stdlib only, and uv handles the Python version.

| Command | Does |
|---|---|
| `build [root]` | Hashes git-visible files and re-outlines only the changed ones into `.pcache/context.md`, which comes out byte-stable. |
| `brief "<task>" [--role R]` | Prints the outline, a fixed rules block, then the role and task last. |
| `stats [session_id] [--logs DIR]` | Shows input, cache write, cache read and hit rate per agent, read from `~/.claude/projects/<cwd>/`. Defaults to the newest session. |
| `--self-test` | Runs the built-in asserts. |

## Rules when running dynamic agents

1. **Before fanning out**, run `build`. It's cheap on later runs because only changed files are re-outlined.
2. **Fresh agents get a `brief` output as their prompt.** Never hand-write the shared part, and never paste a different repo summary into each agent, because one changed byte early on costs the whole prefix.
3. **Use a fork when the agent needs this conversation.** A fork inherits the parent's cached prefix. Use a fresh agent with a brief when it doesn't, which keeps the prefix small and shared across siblings.
4. **Continue an agent with SendMessage instead of spawning a new one.** Its history is already cached.
5. **Keep /loop and ScheduleWakeup delays under 3600s.** Past the 1h TTL, the next turn pays a full cache write again.
6. **Keep the prefix still mid-run.** Don't edit CLAUDE.md, skills or MCP config, and don't switch models, while agents are running.
7. **After the run**, run `stats` and report the TOTAL hit rate in one line. Agents marked `cold` (under 50%) mean their prompt prefix differed. Check rule 2 for them.

`.pcache/` belongs in the target project's `.gitignore`. `build` prints a hint on its first run and never edits the file itself.

Files in this skill

  • SKILL.md3 KB
  • scripts/pcache.py9.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.