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.
npx skills add escapeboy/ai-prompts --skill cache-inspectorgit clone --depth 1 https://github.com/escapeboy/ai-promptsWrote 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.
[](https://agentmods.dev/skills/escapeboy/ai-prompts/cache-inspector)<a href="https://agentmods.dev/skills/escapeboy/ai-prompts/cache-inspector"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/cache-inspector.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00050 | $0.01054 |
| Opus 5 | $0.00025 | $0.00527 |
| Sonnet 5 | $0.00010 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade B, and why
cache-inspector scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| Producing a cost/hit-rate report or tracking trend over sessions | A one-off "is caching on?" check — read `~/.claude/settings/prompt-caching.json` | How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cache-inspector — Prompt Cache Monitor
Inspects the Claude prompt caching system to report hit rates, cost savings, and optimization opportunities. Prompt caching saves 90% on re-reads of large content (system prompts, memories, tool definitions).
When to Use This Skill (and When NOT to)
| Use this skill for | Use a simpler approach for |
|---|---|
| Investigating why a session's token cost is high | A single expensive read you already understand — just cache that content, no analysis needed |
| Diagnosing a low or slow-warming cache hit rate | A fresh session that has simply not warmed yet — wait 2-3 messages before measuring |
| Deciding which memories/prompts are worth caching | Content you already know is under 1024 tokens — it can't cache; expand or merge it directly |
| Producing a cost/hit-rate report or tracking trend over sessions | A one-off "is caching on?" check — read ~/.claude/settings/prompt-caching.json |
Start simple. Reach for this skill only when cache behaviour is actually costing tokens or you need to measure/optimize it — not to confirm a single obvious cache decision.
Usage
/cache-inspector [action]
Quick Examples
/cache-inspector # Show current status (default)
/cache-inspector status # Detailed cache status
/cache-inspector analyze # Performance analysis with trends
/cache-inspector optimize # Get actionable recommendations
/cache-inspector report # Full report (save to file)
/cache-inspector clear # Clear cache (for testing only)
Actions
Each action's full behaviour, options, and exact output shape are in references/actions.md — read it for the detail behind the summaries below.
| Action | Purpose |
|---|---|
status (default) |
Current cache state: active entries, session hits/savings, health verdict. |
analyze |
Deep performance analysis with hit-rate trend, cost impact, and optimization opportunities. |
optimize |
Prioritized, actionable recommendations to raise the hit rate, with an estimated score delta. |
report |
Full report (history, cost breakdown, inventory, TTL timeline, score); --save writes to .claude/learnings/cache-performance.md. |
clear |
Clears all cached content (testing/stale-cache only). Confirms first; next session re-warms at full cost. |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 88 lines · 50 tokens per session scan B da8b0934cefc
cache-inspector is a skill published in the GitHub repository escapeboy/ai-prompts (91 stars, last pushed 11d ago), licensed MIT. It adds 50 tokens to every session and 1,054 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
prompt-optimization
Improve a prompt on the evaluations workbench through a measured loop. Score the baseline first, then duplicate the target column, form a hypothesis from failing rows, edit the copy's prompt draft, run, compare pass rate and cost, and repeat until the numbers hold. Use when the user asks to optimize or improve a…
enhance-prompt
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
prompt-engineer
Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot…
seedance-vocab-en
This skill should be used when an English Seedance 2.0 prompt is slop-heavy, generic, padded with empty quality words, tripping false-positive filters, or needs precise English production vocabulary for camera, lighting, motion, VFX, audio, and constraints.
ideogram4
Prompting patterns for Ideogram 4 text-to-image — best-in-class in-image text rendering and exact color/layout control via structured JSON captions. Use when generating images that need legible on-image text (title cards, thumbnails, logos, signage, CTAs), precise brand colors, or controlled spatial layout. Triggers…