prompt-cache

Cache stable dispatch prompt segments with configurable TTL and telemetry.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill prompt-cache
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-cache
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/prompt-cache
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill prompt-cache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces redundant prompt processing and compute costs by explicitly caching stable portions of multi-turn dispatch prompts and associated telemetry data, improving latency and predictability in large prompt pipelines.

Core Features & Use Cases

  • Breakpoint-driven assembly: fix four deterministic cache breakpoints (system prompt, root AGENTS.md, council AGENTS.md, and skill SKILL.md) to maximize cache hit potential.
  • TTL and telemetry policy: explicit TTL choices, per-project telemetry, and observability to monitor cache effectiveness and savings.
  • Workspace isolation and invalidation: safe cache invalidation when source prompts change to prevent cross-project bleed.
  • Use Case: accelerate repeated prompts across long-running dispatch workflows with stable content.

Quick Start

Initialize prompt-cache with a plan that declares breakpoints, TTL, and telemetry endpoints, then enable caching for repeated prompts to observe savings.

Frequently Asked Questions about prompt-cache

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does prompt caching reduce latency in multi-turn LLM dispatch pipelines?

Prompt caching reduces latency by storing stable portions of multi-turn dispatch prompts at deterministic breakpoints, minimizing redundant processing and compute costs across recurring sessions. This improves predictability for large, multi-turn prompt workflows.

What are cache breakpoints in prompt caching and how do I configure them?

Cache breakpoints are fixed insertion points that maximize cache hit potential for prompt assembly. You configure four deterministic breakpoints across system prompt, root AGENTS.md, council AGENTS.md, and skill SKILL.md to cache stable prompt content.

How do I monitor cache hit rates and compute savings for cached LLM prompts?

You monitor cache effectiveness by integrating telemetry endpoints that report hit rates and savings. Explicit TTL configuration and per-project telemetry observability track cache performance and compute cost reductions for repeated prompts.

How does cache invalidation work when source prompts change in a cached dispatch pipeline?

Cache invalidation uses workspace isolation to safely clear cached prompts when source content changes. This prevents cross-project cache bleed and ensures updated prompts are processed correctly without relying on stale cached data.

Can I use prompt caching for council-driven prompt pipelines across multiple projects?

Yes, prompt caching is designed for multi-turn, council-driven prompt pipelines across root, council, and skill bundles. Workspace isolation ensures safe per-project caching without cross-project bleed when handling recurring prompts.

What TTL settings should I use for caching stable prompt portions in LLM dispatch?

TTL settings depend on prompt volatility and session duration. Explicit TTL configuration lets you control how long stable dispatch prompt portions remain cached, balancing cache hit rates against the need for fresh prompt processing.