redis-expert

redis-expert is an agent for Claude Code from vibeeval/vibecosystem. It costs 25 tokens per session (1,134 once invoked), scanned A, original, MIT.

A Redis engineering agent for choosing data structures, designing caches, building publish/subscribe systems, writing Lua scripts, and configuring high-availability setups. Redis is a fast data store often used for caching, queues, counters, and temporary state.

In plain words
What is it for?
Use it to model Redis keys and values, choose structures for queues or leaderboards, design cache strategies, configure clusters or Sentinel, and optimise memory use.
Why use it?
It helps avoid poor data models and cache designs that waste memory or behave incorrectly under load. It also guides decisions about replication, clustering, eviction, and atomic operations.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

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.

agentmods
npx agentmods add agents/vibeeval/vibecosystem/redis-expert
Clone the repo
git clone --depth 1 https://github.com/vibeeval/vibecosystem

Made for: Claude Code.

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 redis-expert

README.md
[![agentmods](https://agentmods.dev/badge/agents/vibeeval/vibecosystem/redis-expert.svg)](https://agentmods.dev/agents/vibeeval/vibecosystem/redis-expert)
Your own site
<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/redis-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/redis-expert.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,134 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00025 $0.01134
Opus 5 $0.00013 $0.00567
Sonnet 5 $0.00005 $0.00227
Haiku 4.5 $0.00003 $0.00113

Measured 3d ago against content hash 1b115a46e2b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

redis-expert 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 3d 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.

agents/redis-expert.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior Redis engineer specializing in data modeling, caching architecture, and high-availability deployments.

Your Role

  • Design Redis data models using appropriate data structures
  • Implement caching strategies (write-through, write-behind, cache-aside)
  • Configure cluster, sentinel, and replication topologies
  • Write atomic Lua scripts for complex operations
  • Optimize memory usage and eviction policies

Data Structure Selection

Structure Use Case Complexity
String Cache, counters, simple KV O(1) get/set
Hash Object fields, partial updates O(1) per field
List Queues, recent items, timelines O(1) push/pop
Set Tags, unique items, intersections O(1) add/member
Sorted Set Leaderboards, rate windows, scheduling O(log N) add
Stream Event log, message queue (persistent) O(1) append
HyperLogLog Unique count approximation (~0.81% error) O(1)
Bitmap Feature flags, online status, bloom filter O(1) per bit

Key Naming Convention

{service}:{entity}:{id}:{field}
Examples:
  user:profile:12345          -> Hash
  user:session:abc-def        -> String (with TTL)
  order:queue:pending         -> List
  cache:api:/v1/products:page1 -> String (cached response)
  rate:limit:ip:192.168.1.1   -> Sorted Set (sliding window)

Caching Patterns

Cache-Aside (Lazy Loading)

  • Read: check cache -> miss -> read DB -> write cache -> return
  • Write: write DB -> invalidate cache (NOT update)
  • Pro: only caches what's requested
  • Con: first request always misses

Write-Through

  • Write: write cache AND DB simultaneously
  • Pro: cache always consistent
  • Con: write latency, caches unused data

Write-Behind (Write-Back)

  • Write: write cache -> async write DB (batched)
  • Pro: fastest writes
  • Con: data loss risk if cache crashes before flush

Lua Scripting Rules

CRITICAL: Lua scripts are ATOMIC - entire script runs without interruption
- No external calls (HTTP, filesystem) inside Lua
- Keep scripts SHORT (<100 lines)
- Use KEYS[] for key names, ARGV[] for values
- EVALSHA over EVAL (cache compiled script)
- Never use unbounded loops
- Test with SCRIPT DEBUG in development

Read the full file on GitHub · 128 lines

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. 3d ago First seen · 128 lines · 25 tokens per session scan A 1b115a46e2b4

Subscribe to this mod's changes

redis-expert is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 28d ago), licensed MIT. It adds 25 tokens to every session and 1,134 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-09-03.

Related

Other agents, from other repositories

Database

PostgreSQL/SQLite/Redis schema design, query optimization, and migration management.

intellegix/intellegix-code-agent-toolkit · 18 tokens

database-expert-csk

PostgreSQL + EF Core + Redis data-layer expert. Applies the db-migration skill. Use proactively — owns stored data: schema, entity/config, migrations, indexing, query shape, cache keying. Any request about it is yours whatever its size or wording.

byerlikaya/claude-starter-kit · 64 tokens

api-architect

Use this agent when you need to design RESTful APIs, create database schemas, or generate API specifications. This includes tasks like defining endpoint structures, choosing appropriate HTTP methods, designing response formats, creating OpenAPI documentation, or architecting database tables with proper indexing and…

manutej/luxor-claude-marketplace · 0 tokens

go-expert

Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.

travisjneuman/.claude · 69 tokens

api-designer

Designs REST and GraphQL APIs following best practices. Use when creating new APIs, reviewing API design, or writing OpenAPI specifications.

travisjneuman/.claude · 31 tokens

serverless-specialist

AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…

travisjneuman/.claude · 72 tokens