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 johnqtcg/awesome-skills --skill redis-cache-strategygit clone --depth 1 https://github.com/johnqtcg/awesome-skillsWrote 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/johnqtcg/awesome-skills/redis-cache-strategy)<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/redis-cache-strategy"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/redis-cache-strategy/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.
<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/redis-cache-strategy"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/redis-cache-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 78 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 241 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00113 | $0.06217 |
| Opus 5.5 | $0.00045 | $0.02487 |
| Sonnet 5.5 | $0.00023 | $0.01243 |
| Haiku 4.5 | $0.00011 | $0.00622 |
Grade A, and why
redis-cache-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redis Cache Strategy Review
Quick Reference
§1 scope · §2 gates (context, mode, risk, completeness) · §3 depth · §4 degradation modes · §5 the checklist — the only item list · §6 pattern selection · §7 anti-example index · §8 how §5's items are scored · §9 output contract · §10 which reference to load when.
References: cache-patterns.md (patterns in depth) ·
cache-failure-modes.md (stampede / penetration / avalanche / hot key) ·
distributed-locks.md (fencing, renewal, failover) ·
cache-anti-examples.md (AE-1 … AE-13 with code) ·
redis-version-matrix.md (what each Redis version changes).
§1 Scope
In scope — Redis caching strategy for production backend services. The §5 checklist is the scope; it is not restated here, because a second copy of a list is the defect this skill spent a release removing.
Out of scope — delegate to dedicated skills:
- Redis cluster topology, persistence (RDB/AOF), replication config →
redis-best-practise - Application code changes →
go-code-revieweror language-specific reviewer - Security hardening, ACL, TLS →
redis-best-practise
§2 Mandatory Gates
Execute gates sequentially. Each gate has a STOP condition.
Gate 1: Context Collection
| Item | Why it matters | If unknown |
|---|---|---|
| Redis version (major.minor) | Gates several concrete answers this skill gives — see below | Never assume a version. Answer in branches, or mark the version-gated item NOT SCOREABLE |
| Deployment mode (standalone / sentinel / cluster) | Affects key distribution, Lua atomicity scope, lock patterns | Assume standalone — but not for a lock or a multi-key script, where Cluster changes correctness (§5 S7) |
| maxmemory + eviction policy | Determines what happens when cache is full | Ask; critical for correctness |
| Cache role in architecture | Primary cache? L1/L2? Read-through proxy? | Blocking — cannot be assumed |
| Data source type | SQL DB / NoSQL / external API — affects consistency patterns | Blocking — cannot be assumed |
| Read:write ratio | Drives pattern selection (read-heavy → cache-aside; write-heavy → write-behind) | Assume read-heavy |
| Consistency requirement | Eventual (seconds)? Strong? Best-effort? | Blocking — cannot be assumed |
| Peak QPS on cached entities | Determines stampede/hot-key risk | Assume high if unknown |
What ships with it
32 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.
- references/cache-anti-examples.md 9.5 KB
- references/cache-failure-modes.md 17 KB
- references/cache-patterns.md 14 KB
- references/distributed-locks.md 12 KB
- references/redis-version-matrix.md 11 KB
- scripts/check_go_snippets.py 16 KB runs code
- scripts/gen_coverage.py 9.3 KB runs code
- scripts/lint_cache_docs.py 29 KB runs code
- scripts/model_eval.py 19 KB runs code
- scripts/mutation_sweep.py 15 KB runs code
- scripts/run_regression.sh 3.0 KB runs code
- scripts/tests/COVERAGE.md 8.4 KB
- scripts/tests/golden/001_no_consistency_strategy.json 1.5 KB
- scripts/tests/golden/002_no_ttl.json 1.3 KB
- scripts/tests/golden/003_no_degradation.json 1.5 KB
- scripts/tests/golden/004_no_stampede_protection.json 1.6 KB
- scripts/tests/golden/005_lock_no_ttl.json 1.3 KB
- scripts/tests/golden/006_keys_command.json 1.5 KB
- scripts/tests/golden/007_well_formed_cache_aside.json 2.9 KB
- scripts/tests/golden/008_good_write_through.json 2.5 KB
- scripts/tests/golden/009_degraded_no_context.json 1.3 KB
- scripts/tests/golden/010_greenfield_design.json 1.5 KB
- scripts/tests/golden/011_cache_penetration.json 1.6 KB
- scripts/tests/golden/012_write_behind_financial.json 2.0 KB
- scripts/tests/golden/013_no_l1_avalanche.json 2.1 KB
- scripts/tests/golden/014_cross_tenant_leak.json 2.1 KB
- scripts/tests/golden/015_outage_masked_as_miss.json 2.2 KB
- scripts/tests/golden/016_invalidation_race.json 2.6 KB
- scripts/tests/golden/017_lock_expiry_no_fencing.json 2.7 KB
- scripts/tests/test_golden_scenarios.py 17 KB runs code
- scripts/tests/test_skill_contract.py 18 KB runs code
- scripts/trigger_eval.py 11 KB runs code
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.
- 1mo ago First seen · 440 lines · 113 tokens per session scan A 607c34ac1610
redis-cache-strategy is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed 18d ago), licensed MIT. It adds 113 tokens to every session and 6,217 once invoked, about $0.0005 per session on Opus 5.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-30.
Other skills, from other repositories
caching-strategy
Stratégie de cache adaptée à chaque cas d'usage (Redis, Memcached, in-memory, CDN) — quoi cacher, durée de vie, invalidation et cohérence. Se déclenche avec "cache", "Redis", "caching", "mise en cache", "cache invalidation", "CDN", "distributed cache", "réduire les appels à la base". Also triggers on "caching…
redis-patterns
Patterns d'utilisation Redis pour le cache, pub/sub, streams et sessions. Se déclenche avec "Redis", "cache distribué", "pub/sub Redis", "Redis streams", "session store. Also triggers on "Redis cache", "Redis pub/sub".
semantic-caching
Redis semantic caching for LLM apps — vector similarity matching, multi-level cache, TTL strategies, cache warming.
frappe-core-cache
Use when implementing Redis caching, cache invalidation, or distributed locking in Frappe. Prevents stale cache bugs, race conditions from missing locks, and memory bloat from unbounded cache keys. Covers frappe.cache(), @rediscache decorator, cache.getvalue/setvalue, cache invalidation patterns, frappe.lock, TTL…
frappe-ops-performance
Use when tuning MariaDB, configuring Redis memory, sizing Gunicorn workers, setting up CDN, or profiling slow queries. Prevents performance bottlenecks from default configurations, memory exhaustion, and unoptimized database queries. Covers MariaDB tuning, Redis configuration, Gunicorn worker sizing, CDN setup, slow…
nextjs-cache-architecture
Use this skill whenever the user wants to design or implement caching in a Next.js 16+ App Router project — setting up the "use cache" directive, building a cache tag registry, wiring mutations to invalidation utilities, structuring Suspense boundaries for partial prerendering, handling personalized content near cache…