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/iHildy/jules-task-queueWrote 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/rules/ihildy/jules-task-queue/redis)<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.
<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>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.00000 | $0.01971 |
| Opus 5.5 | $0.00000 | $0.00788 |
| Sonnet 5.5 | $0.00000 | $0.00394 |
| Haiku 4.5 | $0.00000 | $0.00197 |
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.
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-casefor file names e.g.user-profile.tsxoruser.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.
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.
- 13d ago First seen · 86 lines · 1,971 tokens per session scan A 241189acc17e
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.
Other cursor rules, from other repositories
redis
This guide provides definitive, actionable best practices for using Redis effectively, focusing on data modeling, performance, security, and cluster-aware client usage to build robust and scalable applications.
full-test-with-db-redis
Run full tests with rootless Podman db and redis.
cache
A set of guidance for using a cache, a temporary data store that keeps frequently needed information available for faster access. It describes cache operations and a shared data center for access to stored data.
spring-boot-lombok
Spring Boot Lombok contract for Maven setup, allowed annotations, and when to prefer Java records.
spring-boot-redis
Spring Boot Redis contract for connection settings, RedisTemplate datastore access, Spring Cache with Redis, and Redis Pub/Sub.
redis_rate_limiting
Complete guide for implementing Redis-based rate limiting with authentication troubleshooting and FastAPI integration.