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 rules/alphabitcore/nexus-gateway/redis-cache-onlygit clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewayWhat 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 | $0.00000 | $0.00568 |
| Opus 5 | $0.00000 | $0.00284 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
redis-cache-only 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 3d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redis is cache-only — no pub/sub (binding)
Nexus Gateway uses Redis for caching only: sessions, IAM cache, rate-limit counters, response cache, desired-state cache, cert cache, quota counters.
Config invalidation across services is the Hub WebSocket change-signal, not Redis pub/sub. See docs/developers/architecture/cross-cutting/foundation/thing-config-sync-architecture.md and docs/developers/architecture/cross-cutting/storage/cache-multi-tier-architecture.md.
What this rule forbids
redis.Subscribe(...),redis.PSubscribe(...)for cross-service event notification.redis.Publish(...)for cross-service signaling.- New code that "broadcasts an invalidation via Redis channel
nexus:config:...".
What's allowed
redis.Set/Get/HGetetc. for plain key-value caching.- Lua scripts on Redis for sliding-window counters (quota, rate-limit).
- Redis-backed LRU promotion in two-tier cert / IAM caches.
Why
The pre-Hub architecture used Redis pub/sub for config invalidation; it had three documented problems (no apply receipt, cold-start divergence, two parallel code paths). The Hub-centric Thing model replaced it. Bringing pub/sub back in any form re-introduces those failure modes.
Enforcement
npm run check:no-redis-pubsub (CI + pre-commit) catches three regression shapes:
- Forbidden pub/sub calls —
redis.Publish/Subscribe/PSubscribe(…)in production Go. - Channel literals — string
nexus:config*appearing anywhere in production code. - Deleted-package re-imports — any Go import of
packages/shared/heartbeat,packages/control-plane/internal/pubsub, orpackages/control-plane/internal_registry. These packages were deleted with the Hub-centric migration; their re-appearance is an unambiguous architectural regression.
Historical context (informational)
Pre-Hub, config invalidation rode nexus:config:shared with payloads "hooks" | "routing" | "credentials" | "all". The pub/sub design had three documented failure modes (no apply receipt, cold-start divergence, two parallel code paths) which the Hub WebSocket change-signal eliminates. The packages named above implemented the old design and are deleted — the names are kept here only so future searches that hit this file get the "use Hub WebSocket instead" answer.
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.
- 3d ago First seen · 43 lines · 0 tokens per session scan A ca366a5cd3b6
redis-cache-only is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (22 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 568 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-08-30.
Other cursor rules, from other repositories
igniter-advanced-features
A guide to the advanced features of Igniter.js, including the background jobs system (BullMQ), the caching and pub/sub store (Redis), and the real-time system for live UI updates.
job-queue
Job queue patterns — use when editing queue package or adding background tasks.
using-archipy-adapters
Using and writing adapters in ArchiPy apps — extras, ports, mocks, boundary errors.
10-deterministic-audit
Enforce deterministic audit behavior — no invented controls, cite authoritative sources, emit traceable artifacts.
recipe_author
How to author a recipe in ks-cookbook.
redis_rate_limiting
Complete guide for implementing Redis-based rate limiting with authentication troubleshooting and FastAPI integration.