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 RaNDoM6913/claude-code-superkit --skill redis-patternsgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/redis-patterns)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/redis-patterns"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/redis-patterns/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/random6913/claude-code-superkit/redis-patterns"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/redis-patterns.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.01987 |
| Opus 5.5 | $0.00024 | $0.00795 |
| Sonnet 5.5 | $0.00012 | $0.00397 |
| Haiku 4.5 | $0.00006 | $0.00199 |
Grade A, and why
redis-patterns 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redis Patterns
Production patterns for Redis as a cache, session store, pub/sub bus, work queue backbone, and distributed coordination primitive.
Use this skill when
- Implementing caching (cache-aside, write-through, write-back)
- Setting up pub/sub or BLPOP-based work queues
- Using Redis data structures (Sorted Sets, Streams, Hash, Sets)
- Configuring ioredis for Node.js production
- Designing key naming and TTL strategies
- Implementing distributed locks with atomic
SET NX EX
Do not use this skill when
- The task requires a message broker with guaranteed delivery — use BullMQ, RabbitMQ, or Kafka
- The task is about Redis server-level configuration / cluster setup
Workflow
- Identify the use case: caching, pub/sub, queue, session, or rate limiting
- Choose the right data structure for the access pattern
- Design keys with
namespace:entity:idconvention - Set TTL on every key (unless intentionally persistent: queues, locks-with-expiry)
- Validate error handling and graceful shutdown
Connection (ioredis — recommended for Node.js)
import Redis from 'ioredis';
export const redis = new Redis({
host: process.env.REDIS_HOST,
port: 6379,
lazyConnect: true,
connectionName: 'api-server',
retryStrategy(times) {
return Math.min(times * 200, 2000);
},
});
redis.on('error', (err) => logger.error({ err }, 'redis'));
redis.on('ready', () => logger.info('redis ready'));
- Singleton client;
lazyConnectdefers connection until first command retryStrategyfor exponential backoff- Separate dedicated subscriber connection for pub/sub (can't mix with commands)
- BullMQ:
maxRetriesPerRequest: nullis mandatory
Cache-Aside Pattern
async function getUser(id: string): Promise<User> {
const key = `cache:user:${id}`;
const cached = await redis.get(key);
if (cached) return JSON.parse(cached);
const user = await db.users.findUnique({ where: { id } });
if (user) await redis.set(key, JSON.stringify(user), 'EX', 300);
return user;
}
async function invalidateUser(id: string) {
await redis.del(`cache:user:${id}`);
}
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 · 261 lines · 61 tokens per session scan A 65f060aa7f14
redis-patterns is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 8d ago), licensed MIT. It adds 61 tokens to every session and 1,987 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
spring-cache
Spring Cache abstraction for Spring Boot 3.x. Covers @Cacheable, @CacheEvict, @CachePut, cache managers (Caffeine, Redis, EhCache), TTL configuration, cache keys, conditional caching, and cache synchronization. USE WHEN: user mentions "spring cache", "@Cacheable", "@CacheEvict", "cache manager", "Caffeine cache"…
caching-strategies
Application caching patterns. Redis caching, in-memory caches, HTTP caching, cache invalidation strategies, cache-aside, write-through, and CDN caching. USE WHEN: user mentions "caching", "cache invalidation", "Redis cache", "HTTP cache", "CDN caching", "cache-aside", "write-through", "TTL", "stale-while-revalidate"…
bullmq-specialist
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.
redis-caching-and-pubsub
Architecting high-performance caching strategies, Cache-Aside/Write-Through/Write-Behind patterns, Redis Pub/Sub, Streams, eviction policies, distributed locking (Redlock), and memory optimization. Use when implementing Redis caching, real-time messaging, rate limiting, or session management.
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".