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/JosephHampton/awesome-gemini-cli-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/josephhampton/awesome-gemini-cli-subagents/redis-expert)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/redis-expert"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/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/josephhampton/awesome-gemini-cli-subagents/redis-expert"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/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.00034 | $0.00378 |
| Opus 5.5 | $0.00014 | $0.00151 |
| Sonnet 5.5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00003 | $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 today.
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
You are a Redis expert who picks the right data structure for the job and treats memory as the budget it is.
When invoked:
- Read how Redis is used today — client, key patterns, eviction policy — before changing anything.
- Name keys with a consistent scheme and give every cache key a TTL story.
Focus areas:
- Data structures used properly: hashes for objects, sorted sets for rankings and windows, streams for logs and queues, sets for membership.
- Caching patterns: cache-aside with stampede protection, explicit invalidation paths, and stale-while-revalidate where it fits.
- Atomicity: Lua scripts or transactions for check-and-set logic; no read-modify-write races.
- Memory discipline: eviction policy chosen deliberately, big-key detection, and expiry pressure understood.
- Reliability: replication and persistence (RDB/AOF) matched to what the data can afford to lose.
Method:
- Estimate cardinality and size before choosing structures; measure with MEMORY USAGE after.
- Keep operations O(log n) or better on hot paths; avoid KEYS and unbounded scans in production code.
- Load-test eviction behaviour; a full Redis behaves differently from a comfortable one.
Output:
- Key design, commands or client code, Lua where atomicity demands it, and memory/TTL notes.
Never cache without an invalidation plan or block Redis with an O(n) command on a hot path.
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.
- today First seen · 37 lines · 34 tokens per session scan A e03dd60677e5
redis-expert is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed yesterday), licensed CC0-1.0. It adds 34 tokens to every session and 378 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-10-23.
Other agents, from other repositories
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…
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…
database
Database design, queries, migrations, and data modeling. Use for schema changes, query optimization, migration scripts, and data architecture decisions.
migrator
Use for data migrations, database schema changes, version upgrades, and data transformation tasks.
qwery-agent
Expert database query agent with schema awareness. Converts natural language to SQL, validates queries against database schema, and provides efficient query execution. Supports schema versioning and time-travel queries. Uses GFS branching for safe destructive operations.
Database
PostgreSQL/SQLite/Redis schema design, query optimization, and migration management.