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 agentmods add agents/0xfurai/claude-code-subagents/redis-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/redis-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/redis-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/redis-expert.svg" alt="Measured on agentmods" 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.00020 | $0.00385 |
| Opus 5 | $0.00010 | $0.00192 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
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 2d 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.
What it actually says
Focus Areas
- In-memory data storage techniques
- Key-value pair management
- Redis replication and persistence
- Efficient caching strategies
- Data eviction policies
- Real-time data analytics
- Redis Cluster and sharding
- Lua scripting with Redis
- Pub/Sub messaging patterns
- Redis security and authentication
Approach
- Use Redis for fast in-memory data retrieval
- Manage data using appropriate data structures (strings, hashes, lists, sets)
- Implement persistence with RDB and AOF
- Configure master-slave replication for high availability
- Apply optimal data eviction policies (LRU, LFU, etc.)
- Design Redis Cluster for distributed data
- Use Lua scripts to minimize network round trips
- Secure Redis with proper authentication and access control
- Monitor performance using Redis native tools
- Optimize memory usage according to data access patterns
Quality Checklist
- Data is organized using suitable Redis data types
- Persistence is configured correctly for durability
- Replication is set up for fault tolerance
- Appropriate eviction policies are applied
- Clustering is implemented for scalability
- Lua scripts are optimized for performance
- Security features are enabled and configured
- Monitoring dashboards are in place
- Access to Redis is logged and audited
- Performance benchmarks show optimal latency
Output
- Redis configuration files with best practices
- Documentation on chosen data structures and their use cases
- Scripts to set up replication and clustering
- Guides for implementing persistence strategies
- Test cases for security and access control
- Performance reports from Redis monitoring tools
- Lua scripts for critical processing tasks
- Examples of Pub/Sub use cases
- Automation scripts for managing Redis instances
- Detailed installation and setup instructions
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.
- 2d ago First seen · 57 lines · 20 tokens per session scan A 93757b9ebc4d
redis-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 20 tokens to every session and 385 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.
Other agents, from other repositories
kv-optimizer
This agent should be used when the user asks to "optimize kv", "improve kv performance", "reduce kv costs", "kv best practices", "make kv faster", or mentions performance tuning, cost optimization, or caching strategies for Cloudflare Workers KV. The agent analyzes KV usage patterns, identifies anti-patterns, suggests…
data
Use when designing database schemas, writing migrations, optimizing queries, or planning caching strategies.
messaging-cache
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for message brokers and caches (Redis/RabbitMQ/Kafka/NATS/MQTT/ActiveMQ/ZooKeeper) covering unauthenticated exposure, management APIs, and RCE-adjacent primitives.
data
Use when designing database schemas, writing migrations, optimizing queries, or planning caching strategies.
database-optimizer
Expert database optimizer specializing in modern performance tuning, query optimization, and scalable architectures. Masters advanced indexing, N+1 resolution, multi-tier caching, partitioning strategies, and cloud database optimization. Handles complex query analysis, migration strategies, and performance monitoring.…
qdrant-expert
Configure and operate the vector store in production. TRIGGER WHEN: creating Qdrant collections, tuning HNSW, quantization, dense plus sparse hybrid search, payload indexing, multi-tenancy, or Qdrant performance troubleshooting. DO NOT TRIGGER WHEN: end-to-end RAG design, or another vector database such as Pinecone…