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 caiaffa/claude-code-ultimate-engineering-system --skill redis-bullmq-systemsgit clone --depth 1 https://github.com/caiaffa/claude-code-ultimate-engineering-systemWrote 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/caiaffa/claude-code-ultimate-engineering-system/redis-bullmq-systems)<a href="https://agentmods.dev/skills/caiaffa/claude-code-ultimate-engineering-system/redis-bullmq-systems"><img src="https://agentmods.dev/badge/skills/caiaffa/claude-code-ultimate-engineering-system/redis-bullmq-systems/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/caiaffa/claude-code-ultimate-engineering-system/redis-bullmq-systems"><img src="https://agentmods.dev/badge/skills/caiaffa/claude-code-ultimate-engineering-system/redis-bullmq-systems.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.00037 | $0.00656 |
| Opus 5 | $0.00018 | $0.00328 |
| Sonnet 5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
redis-bullmq-systems 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 9d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Make asynchronous job systems predictable, debuggable, and safe under retries, backlogs, partial failures, and restarts.
When to use
- Designing workers or queues.
- Reviewing BullMQ processing logic.
- Investigating job duplication, lag, or stuck jobs.
- Tuning throughput and concurrency.
Handoff
- Receives from: backend-platform-engineer (implementation).
- Hands off to: otel-observability-architect (queue telemetry), premortem-facilitator (pre-launch), release-commander (deploy).
BullMQ reality check
- BullMQ is at-least-once, never exactly-once. Design for it.
- Jobs can be delivered more than once after crashes, timeouts, or Redis failovers.
- Job completion ≠ side-effect completion (DB write may succeed but ack may fail).
- Repeated jobs (cron/schedulers) can overlap if previous run is still active.
Design checklist
- Idempotency — where is the dedup boundary? (database unique constraint? Redis SET NX? application check?)
- Retry policy — which errors are retryable? what's the backoff? what's the max attempts? what happens at max?
- Dead letter — where do permanently failed jobs go? who monitors? who resolves?
- Concurrency — what's the per-worker concurrency? what happens at 2x/10x job volume?
- Queue isolation — are noisy/slow job types separated from critical ones?
- Graceful shutdown — does the worker finish in-progress jobs before exit? timeout?
- Stuck jobs — how are stalled jobs detected and recovered?
stalledIntervalconfigured? - Backlog — what metrics show queue depth, age, and processing latency?
Common failure patterns
| Pattern | What goes wrong | Fix |
|---|---|---|
| No idempotency key | Retry creates duplicate business effects | Dedup at DB or application level |
| Unbounded retries | Poison job retried forever, blocks queue | Max attempts + dead letter |
| Shared queue for all job types | Slow bulk job starves time-sensitive jobs | Separate queues per priority/type |
| No stalled job detection | Worker crash leaves job in "active" forever | Configure stalledInterval + maxStalledCount |
| Cron overlap | Previous run still active when next starts | Mutex lock or jobId-based dedup |
| No backlog alerting | Queue grows for hours before anyone notices | Alert on queue depth + oldest job age |
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.
- 9d ago First seen · 51 lines · 37 tokens per session scan A 5e10b5bf7e6c
redis-bullmq-systems is a skill published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 656 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-30.
Other skills, from other repositories
pinecone
Managed vector DB for production RAG and search.
redis-js
Work with the Upstash Redis JavaScript/TypeScript SDK for serverless Redis operations. Use for caching, session storage, rate limiting, leaderboards, full-text search (querying, filtering, aggregating with @upstash/redis search extension), and all Redis data structures. Supports automatic serialization/deserialization…
byted-milvus
Manages Milvus on Volcano Engine (Volcengine): provision/inspect/scale/delete clusters and run collection + CRUD/search operations via bundled CLIs. Use when the user mentions Milvus + Volcengine/Volcano Engine or asks to operate Milvus there.
vector-db
Vector database expert for embeddings, similarity search, RAG patterns, and indexing strategies.
redis-search
Redis Search guidance covering FT.CREATE schema design, field type selection (TEXT, TAG, NUMERIC, GEO, GEOSHAPE, VECTOR, JSON path), DIALECT 2 query syntax, FT.SEARCH / FT.AGGREGATE / FT.HYBRID command selection, vector similarity with HNSW or FLAT, hybrid retrieval combining lexical and vector ranking, RAG pipelines…
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"…