prompt-cache-control

prompt-cache-control is a plugin for Claude Code from davila7/claude-code-templates. Its token cost is not measured, scanned A, original, MIT.

A prompt-cache monitor that shows how many tokens were reused, stored, or sent outside the cache, along with the cache's remaining lifetime. Prompt caching stores parts of requests temporarily so later requests can reuse them.

In plain words
What is it for?
Use it to inspect cache use per request, view cache lifetime, and choose cache actions from the coding-agent interface.
Why use it?
It helps explain cache-related request behavior and shows when a cache is about to expire, so you can decide whether to continue, shorten the conversation, or clear it.

Plugin for Claude Code

Written for Claude Code: a Claude Code plugin manifest. Also seen: mentions Claude Code.

Good fit Use it to inspect cache use per request, view cache lifetime, and choose cache actions from the coding-agent interface.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add davila7/claude-code-templates
/plugin install prompt-cache-control
About the project

Claude Code Templates is a command-line tool and catalogue for configuring Anthropic’s Claude Code with agents, commands, settings, hooks, integrations, skills, and project templates. Developers use it to browse and install reusable components for their coding workflows. The catalogue includes many of these Claude Code components.

davila7/claude-code-templates · 32,738 stars · on GitHub · aitmpl.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/davila7/claude-code-templates

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for prompt-cache-control

README.md
[![agentmods](https://agentmods.dev/badge/plugins/davila7/claude-code-templates/prompt-cache-control/github.svg)](https://agentmods.dev/plugins/davila7/claude-code-templates/prompt-cache-control)
Your own site
<a href="https://agentmods.dev/plugins/davila7/claude-code-templates/prompt-cache-control"><img src="https://agentmods.dev/badge/plugins/davila7/claude-code-templates/prompt-cache-control/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for prompt-cache-control

Your own site · 80×15
<a href="https://agentmods.dev/plugins/davila7/claude-code-templates/prompt-cache-control"><img src="https://agentmods.dev/badge/plugins/davila7/claude-code-templates/prompt-cache-control.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

prompt-cache-control scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cli-tool/components/mods/observability/prompt-cache-control/.claude-plugin/plugin.json · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

{
  "name": "prompt-cache-control",
  "version": "0.1.0",
  "description": "Prompt-cache meter above the Claude Code prompt: how many tokens each request read from, wrote to and sent past the cache, a live countdown to the cache's expiry, and what to do about it (keep going, compact or clear). The TTL follows Claude Code's own rules for your account (1 hour on a Claude subscription, 5 minutes on an API key, cloud provider or usage credits, plus the TTL variables and setting) and corrects itself from request timing. When Claude Code will compact an idle conversation by itself, it counts down to that too. /cache opens a per-turn table.",
  "author": {
    "name": "claude-code-templates",
    "url": "https://www.aitmpl.com"
  },
  "repository": "https://github.com/davila7/claude-code-templates",
  "license": "MIT",
  "keywords": [
    "mod",
    "function-hooks",
    "observability",
    "prompt-caching",
    "cost"
  ],
  "userConfig": {
    "ttl": {
      "type": "string",
      "title": "Cache lifetime",
      "description": "How long the cache lives after a request: auto follows Claude Code's own rules (FORCE_PROMPT_CACHING_5M, CLAUDE_CODE_PROMPT_CACHE_TTL, the promptCacheTtl setting, ENABLE_PROMPT_CACHING_1H, then 1 hour on a Claude subscription and 5 minutes on an API key, cloud provider or usage credits) and corrects itself from request timing; 5m or 1h pins it",
      "default": "auto",
      "options": [
        "auto",
        "5m",
        "1h"
      ]
    },
    "warnSeconds": {
      "type": "number",
      "title": "Warn before expiry (s)",
      "description": "Seconds left on the countdown at which the band turns yellow and a toast reminds you the cache is about to lapse",
      "default": 60
    },
    "compactAtTokens": {
      "type": "number",
      "title": "Large context (tokens)",
      "description": "From this prompt size up, an expired cache suggests /compact (or /clear) before you pay to write the whole prefix again",
      "default": 100000

Read the full file on GitHub · 68 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago Changed · +6 lines a1e7174c1731
  2. 14d ago Changed 1edb00c4b750
  3. 15d ago Changed c4cd8f3638ef
  4. 17d ago First seen · 62 lines scan A 7f79b02f08b4

Subscribe to this mod's changes

prompt-cache-control is a plugin published in the GitHub repository davila7/claude-code-templates (32,738 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.