caching-strategy

caching-strategy is a skill for Claude Code, Codex from mercuryPark/oc-setup. It costs 27 tokens per session (308 once invoked), scanned A, original, MIT.

A guide to caching data in browsers, content delivery networks (CDNs), and Redis, a fast in-memory data store. It also covers cache-aside patterns and ways to remove or refresh outdated cached data.

In plain words
What is it for?
Use it to design browser, CDN, or Redis caching; set time-to-live rules; refresh cached data after changes; and improve database-heavy applications.
Why use it?
Caching can reduce repeated database work and speed up responses, but stale data and cache failures can create bugs. The guide helps choose expiration and invalidation rules and handle fallbacks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit Use it to design browser, CDN, or Redis caching; set time-to-live rules; refresh cached data after changes; and improve database-heavy applications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mercurypark/oc-setup/caching-strategy
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.

Any agent
npx skills add mercuryPark/oc-setup --skill caching-strategy
Clone the repo
git clone --depth 1 https://github.com/mercuryPark/oc-setup

Made for: Claude Code, Codex.

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 caching-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/mercurypark/oc-setup/caching-strategy.svg)](https://agentmods.dev/skills/mercurypark/oc-setup/caching-strategy)
Your own site
<a href="https://agentmods.dev/skills/mercurypark/oc-setup/caching-strategy"><img src="https://agentmods.dev/badge/skills/mercurypark/oc-setup/caching-strategy.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 308 The whole file, excluding the scripts and references it only reads on demand.
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.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00308
Opus 5 $0.00014 $0.00154
Sonnet 5 $0.00005 $0.00062
Haiku 4.5 $0.00003 $0.00031

Measured 7d ago against content hash 97f0a5fdc1ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

caching-strategy 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 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.

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.

templates/skills/caching-strategy/SKILL.md · 57 lines

What it actually says

Caching Strategy

Multi-Layer Caching

Browser Cache

Cache-Control: public, max-age=3600
ETag: "abc123"

CDN Cache

  • Cache static assets at edge
  • Purge via API on deployments
  • Use versioned filenames

Application Cache (Redis)

const cacheKey = `user:${userId}`
let user = await redis.get(cacheKey)

if (!user) {
  user = await db.query('SELECT * FROM users WHERE id = $1', [userId])
  await redis.setex(cacheKey, 3600, JSON.stringify(user))
}

Cache Invalidation

Strategies

  1. Time-based: TTL
  2. Event-based: On data change
  3. Version-based: Increment version key

Pattern: Cache-aside

async function getUser(id: string) {
  const cached = await cache.get(id)
  if (cached) return cached
  
  const user = await db.get(id)
  await cache.set(id, user, 3600)
  return user
}

Best Practices

  • Set appropriate TTL based on data volatility
  • Implement cache warming for critical data
  • Monitor cache hit rates
  • Handle cache failures gracefully (fallback to DB)
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. 7d ago First seen · 57 lines · 27 tokens per session scan A 97f0a5fdc1ff

Subscribe to this mod's changes

caching-strategy is a skill published in the GitHub repository mercuryPark/oc-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 308 once invoked, about $0.0001 per session on Opus 5. 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-08-31.