cline-pin-timestamp

Adds a fixed timestamp to optimize Cline's prompt-caching efficiency.

113|8|Updated May 28, 2026
One-click install
npx skills add https://github.com/OnlyTerp/prompt-cache-skills --skill cline-pin-timestamp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cline-pin-timestamp
Source: https://github.com/OnlyTerp/prompt-cache-skills/tree/main/skills/cline-pin-timestamp
Command: npx skills add https://github.com/OnlyTerp/prompt-cache-skills --skill cline-pin-timestamp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents cache invalidation by pinning the system-prompt timestamp in Cline, ensuring cache hit rates are maximized and reducing unnecessary API costs.

Core Features & Use Cases

  • Cache Hit Rate Improvement: Ensures system-prompt cache is valid by pinning the timestamp.
  • Cost Reduction: Mitigates API costs by optimizing cache usage.
  • Use Case: For developers using Cline, applying this Skill will result in higher cache hit rates, saving API costs and improving efficiency.

Quick Start

Apply this skill to Cline to pin the system-prompt timestamp.

Frequently Asked Questions about cline-pin-timestamp

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

FAQPage Schema
How do I prevent cache invalidation in Cline's system prompt?

Prevent cache invalidation in Cline by pinning the system-prompt timestamp, which fixes timestamp computation to maximize cache hit rates and reduce API costs.

Why does my Cline system prompt keep triggering cache invalidation?

Cline cache invalidation occurs because the system-prompt timestamp changes dynamically, but pinning it at initialization ensures the cache remains valid across requests.

Can I reduce API costs by fixing the timestamp computation in Cline?

Yes, you can reduce API costs by fixing timestamp computation in Cline, as pinning the system-prompt timestamp maximizes cache hit rates and avoids unnecessary token reprocessing.

What is the best way to maximize cache hit rates for Cline API requests?

The best way to maximize cache hit rates for Cline API requests is pinning the system-prompt timestamp at initialization, preventing dynamic changes that invalidate the prompt cache.

Does applying timestamp pinning require modifying specific Cline source files?

Yes, applying timestamp pinning requires modifying Cline's 'src/core/prompts/system.ts' file to compute and store the timestamp at initialization instead of dynamically updating it.