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 parisgroup-ai/imersao-ia-setup --skill redis-designgit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/redis-design)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/redis-design"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/redis-design/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/parisgroup-ai/imersao-ia-setup/redis-design"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/redis-design.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.00071 | $0.01645 |
| Opus 5.5 | $0.00028 | $0.00658 |
| Sonnet 5.5 | $0.00014 | $0.00329 |
| Haiku 4.5 | $0.00007 | $0.00164 |
Grade A, and why
redis-design 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 19d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redis Design Skill
Key Naming Convention
MANDATORY FORMAT: {env}:{app}:{entity}:{id}[:suffix]
| Component | Example | Purpose |
|---|---|---|
| env | prod, stg, dev |
Environment isolation |
| app | api, worker, web |
Application namespace |
| entity | user, session, cache |
Data type |
| id | usr_123, abc456 |
Unique identifier |
| suffix | :v1, :meta |
Versioning/subkey |
# Good
prod:api:session:sess_abc123
prod:api:cache:user:usr_789:v1
prod:api:ratelimit:usr_789:28381681
# Bad - no namespace, collision risk
session:abc123
user:789
Hash Tags for Clustering
CRITICAL: Related keys MUST share hash tag for atomic operations.
# Keys on SAME slot (required for MULTI/EXEC)
{user:123}:profile
{user:123}:sessions
{user:123}:preferences
# WRONG - different slots, MULTI fails
user:123:profile
user:123:sessions
Data Structure Selection
| Use Case | Structure | Why NOT alternatives |
|---|---|---|
| Object with fields | Hash | String+JSON = full deserialize |
| Unique collection | Set | List allows duplicates |
| Ranked data | Sorted Set | Manual sorting = O(n log n) |
| Queue | Stream | List = no consumer groups |
| Counter | String+INCR | Hash HINCRBY if grouped |
| Time-series | Stream | Sorted Set = manual cleanup |
| Events (fire-forget) | Pub/Sub | Stream = unnecessary persistence |
| Events (guaranteed) | Stream | Pub/Sub = no replay/ACK |
Cache Patterns
| Pattern | When to Use | Implementation |
|---|---|---|
| Cache-Aside | Read-heavy, tolerates stale | App reads cache, misses hit DB |
| Write-Through | Consistency critical | Write DB + cache atomically |
| Write-Behind | Write-heavy, eventual OK | Queue writes, batch to DB |
Stampede Prevention:
# Probabilistic early refresh: refresh at TTL * 0.8 randomly
SET key value EX 300
# When TTL < 60 AND random() < 0.1 → background refresh
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.
- 19d ago First seen · 217 lines · 71 tokens per session scan A 9cf82e48c7ea
redis-design is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 18d ago), licensed MIT. It adds 71 tokens to every session and 1,645 once invoked, about $0.0003 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-06.
Other skills, from other repositories
cache-design
Design a caching strategy for an application — pattern selection, key design, TTL, and eviction policy. Use when asked to "add caching to this", "design a cache strategy", or "what should we cache".
ecommerce-caching
Improve store performance with a layered caching strategy — CDN edge caching, Redis application cache, and smart cart-aware invalidation.
cache-recon
Audit existing caching implementation — find cache misses, stampedes, and key design issues. Use when asked to "audit our caching", "why is our hit rate low", or "find cache stampedes".
woocommerce-performance
Fix slow WooCommerce stores by optimizing database queries, clearing transients, enabling Redis object caching, and configuring page caching.
caching-strategies
Design multi-tier caching architectures for web applications — cache-aside vs write-through vs write-behind, TTL design, cache invalidation, Redis patterns, CDN configuration, browser caching, and stampede prevention. Use when choosing a caching pattern, designing cache invalidation strategies, implementing Redis…
cache-strategy-invalidation-expert
Redis caching patterns, cache-aside, write-through, TTL strategies, and invalidation. Activate on: caching, Redis, cache invalidation, cache-aside, write-through, TTL, CDN cache, stale-while-revalidate. NOT for: CDN/reverse proxy setup (use api-gateway-reverse-proxy-expert), database query optimization (use…