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 mercuryPark/oc-setup --skill redis-pubsubgit clone --depth 1 https://github.com/mercuryPark/oc-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/mercurypark/oc-setup/redis-pubsub)<a href="https://agentmods.dev/skills/mercurypark/oc-setup/redis-pubsub"><img src="https://agentmods.dev/badge/skills/mercurypark/oc-setup/redis-pubsub.svg" alt="Measured on agentmods" 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.00032 | $0.00234 |
| Opus 5 | $0.00016 | $0.00117 |
| Sonnet 5 | $0.00006 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
redis-pubsub 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 7d 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.
What it actually says
Redis Pub/Sub Guide
Pattern Selection
When to Use Pub/Sub
- Real-time notifications across servers
- Chat room message broadcasting
- Event-driven architecture
When NOT to Use
- Persistent message queuing (use Streams)
- Complex routing (use message queues)
Implementation
Basic Pub/Sub
// Publisher
redisClient.publish('chat:room:123', JSON.stringify(message))
// Subscriber
redisClient.subscribe('chat:room:123')
redisClient.on('message', (channel, message) => {
io.to(channel).emit('new_message', JSON.parse(message))
})
Channel Naming
- Pattern:
{service}:{resource}:{id} - Examples:
chat:room:123notification:user:456system:broadcast
Best Practices
- Handle reconnection automatically
- Implement channel cleanup
- Monitor memory usage
- Use pattern matching carefully
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.
- 7d ago First seen · 47 lines · 32 tokens per session scan A 60e3a6dbee33
redis-pubsub is a skill published in the GitHub repository mercuryPark/oc-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 234 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
background-job-orchestrator
Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues. Implements retries, scheduling, priority queues, and worker management. Use for async task processing, email campaigns, report generation, batch operations. Activate on "background job", "async task", "queue", "worker", "BullMQ"…
nw-sd-patterns
Core distributed systems patterns - load balancing, caching, sharding, consistent hashing, message queues, rate limiting, CDN, Bloom filters, ID generation, replication, conflict resolution, CAP theorem.
cache-strategy
Design and implement caching layers for APIs and web applications using Redis or Memcached. Use when you need to reduce database load, improve response times, or handle traffic spikes. Covers cache-aside, write-through, and write-behind patterns, TTL strategies, cache invalidation, and stampede prevention. Trigger…
bull-mq
You are an expert in BullMQ, the high-performance job queue for Node.js built on Redis. You help developers build reliable background processing systems with delayed jobs, rate limiting, prioritization, repeatable cron jobs, job dependencies, concurrency control, and dead-letter handling — powering email sending…
spring-data-redis
Use when implementing caching, session storage, rate limiting, or any Redis integration. Covers cache-aside pattern, key naming, TTL strategy, and serialization config.
python-redis-module-skill
A Python integration guide for adding Redis to an existing FastAPI project. Redis is a fast shared data store commonly used for temporary data, sessions, locks, counters, and messages.