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.
git clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/agents/vibeeval/vibecosystem/redis-expert)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/redis-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/redis-expert/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/agents/vibeeval/vibecosystem/redis-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/redis-expert.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.00025 | $0.01134 |
| Opus 5.5 | $0.00010 | $0.00454 |
| Sonnet 5.5 | $0.00005 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00113 |
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 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 — 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
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 · 128 lines · 25 tokens per session scan A 1b115a46e2b4
redis-expert is an agent published in the GitHub repository vibeeval/vibecosystem (538 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 1,134 once invoked, about $0.0001 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 agents, from other repositories
Database
PostgreSQL/SQLite/Redis schema design, query optimization, and migration management.
mb-backend
Backend specialist for memory-bank /mb work stages. APIs, services, database, async/concurrency, server-side business logic. Falls back to mb-developer when stage is generic.
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.
backend-platform-engineer
Builds and reviews backend services — NestJS modules, APIs, Postgres access, Redis/BullMQ workers, async workflows. Use for implementation, code, tests, debugging and refactoring. Escalates architecture-level decisions to principal-engineer.
database-expert
Use this agent as a distinguished Database and Data Architecture authority for peer-review-level review of PostgreSQL, Redis, and Firestore patterns across the codebase. Covers query optimization, schema design, migration safety, connection pooling, caching strategy, data modeling, consistency patterns, and polyglot…
backend-engineer
Use this agent when the task involves API endpoints, database schema design, Prisma migrations, authentication, authorization, server-side validation, middleware, or business logic. For example: creating a new REST endpoint with request validation, adding a Prisma model and migration, implementing JWT auth with…