redis

redis is a cursor rule for Cursor from iHildy/jules-task-queue. It costs 0 tokens per session (1,971 once invoked), scanned A, original, MIT.

A set of rules for using Redis, an in-memory data store commonly used for caching and fast application data access.

In plain words
What is it for?
Use it when writing code that connects to Redis, especially in applications that need pooled connections, secure remote access, or recovery from temporary failures.
Why use it?
It guides connection handling, retries, timeouts, pooling, security, and library maintenance to avoid common reliability and performance problems.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when writing code that connects to Redis, especially in applications that need pooled connections, secure remote access, or recovery from temporary failures.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ihildy/jules-task-queue/redis
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.

Clone the repo
git clone --depth 1 https://github.com/iHildy/jules-task-queue

Made for: Cursor.

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

README.md
[![agentmods](https://agentmods.dev/badge/rules/ihildy/jules-task-queue/redis/github.svg)](https://agentmods.dev/rules/ihildy/jules-task-queue/redis)
Your own site
<a href="https://agentmods.dev/rules/ihildy/jules-task-queue/redis"><img src="https://agentmods.dev/badge/rules/ihildy/jules-task-queue/redis/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.

agentmods 80×15 button for redis

Your own site · 80×15
<a href="https://agentmods.dev/rules/ihildy/jules-task-queue/redis"><img src="https://agentmods.dev/badge/rules/ihildy/jules-task-queue/redis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,971 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00000 $0.01971
Opus 5.5 $0.00000 $0.00788
Sonnet 5.5 $0.00000 $0.00394
Haiku 4.5 $0.00000 $0.00197

Measured 13d ago against content hash 241189acc17e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

redis 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 13d 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.

.cursor/rules/redis.mdc · 86 lines

How it starts

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

Project Tech Stack:

ALWAYS USE THE FOLLOWING IN CONJUNCTION WITH EACHOTHER TO HAVE A SAFE CODEBASE WHERE WE CAN MOVE FAST AND BREAK NOTHING

  • Next.js

  • Typescript + ESlint

  • Zod + Prisma + tRPC + React Query

  • Prisma (supabase) + Redis

  • ShadCN + TailwindCSS v4

  • Vitest Unit Tests

  • General Best Practices

    • Follow official Redis documentation and community best practices.
    • Use the most recent stable version of the Redis client library for your language.
    • Regularly update the Redis server and client libraries to benefit from bug fixes, performance improvements, and security patches.
  • Connection Management

    • Connection Pooling: Use connection pooling to reduce the overhead of creating new connections for each operation. This significantly improves performance, especially in high-traffic scenarios.
    • Connection Timeout: Configure appropriate connection timeouts to prevent indefinite blocking in case of network issues.
    • Retry Logic: Implement retry logic with exponential backoff for transient connection errors.
    • Secure Connections: When connecting to a remote Redis instance, always use TLS/SSL encryption (redis+ssl://) to protect data in transit, especially when dealing with sensitive information. Ensure proper certificate validation.
  • Data Modeling and Serialization

    • Key Naming: Use consistent and meaningful key naming conventions. Consider using namespaces or prefixes to organize keys and avoid collisions.
    • Consistent Case: Maintain a consistent casing convention (e.g., camelCase for variables, PascalCase for components). Use kebab-case for file names e.g. user-profile.tsx or user.router.ts
    • Data Serialization: Choose an efficient serialization format (e.g., JSON, Protocol Buffers, MessagePack) and use it consistently. Consider the trade-offs between human readability, storage space, and serialization/deserialization performance.
    • Smaller Values: Redis works best with smaller values. Break larger data structures into smaller chunks and distribute them across multiple keys. This improves memory utilization and performance.
    • Data Types: Leverage Redis's rich data types (strings, lists, sets, sorted sets, hashes, streams) effectively to optimize data storage and operations. Choose the data type that best suits the use case.

Read the full file on GitHub · 86 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. 13d ago First seen · 86 lines · 1,971 tokens per session scan A 241189acc17e

Subscribe to this mod's changes

redis is a cursor rule published in the GitHub repository iHildy/jules-task-queue (17 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,971 tokens. 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-02.