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 cookieMonsterDev/agents-skills --skill bullmq-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-skillsWrote 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/cookiemonsterdev/agents-skills/bullmq-docs)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/bullmq-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/bullmq-docs/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/cookiemonsterdev/agents-skills/bullmq-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/bullmq-docs.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.00086 | $0.01079 |
| Opus 5 | $0.00043 | $0.00540 |
| Sonnet 5 | $0.00017 | $0.00216 |
| Haiku 4.5 | $0.00009 | $0.00108 |
Grade A, and why
bullmq-docs 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 8d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BullMQ questions are easy to answer from stale memory or Bull (v3) patterns that do not apply to BullMQ. Use this skill to ground answers in the official BullMQ documentation and return the closest authoritative page instead of generic Redis queue advice.
When to Use
Use this skill when the request is about:
- BullMQ concepts: queues, workers, jobs, and Redis-backed execution
- Creating queues, adding jobs, and processing jobs with workers
- Priorities, delays, repeatable jobs, cron schedules, and job schedulers
- Retries, backoff, failure handling, and stalled job recovery
- Concurrency, rate limiting, parallelism, and sandboxed processors
- Flows and parent-child job dependencies
- Events, metrics, telemetry, and observability
- Redis compatibility, hosting, and cluster considerations
- NestJS integration and production deployment guidance
- BullMQ patterns: deduplication, idempotency, bulk jobs, and manual retry
Do not use this skill for:
- Raw Redis server configuration unrelated to BullMQ usage. Use
redis-docsinstead. - RabbitMQ or Kafka messaging patterns. Use
rabbitmq-docsorkafka-docsinstead. - Legacy Bull (v3) API questions unless the user explicitly asks about Bull docs linked from BullMQ.
- Python, Rust, Elixir, or PHP queue libraries unless the question is about those BullMQ ports documented on docs.bullmq.io.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Quick start and core concepts
- Connections and Redis setup
- Queues, workers, and jobs
- Scheduling, retries, and failure handling
- Flows and advanced job relationships
- Events, metrics, and telemetry
- Patterns and production guidance
- NestJS and framework integration
If you need a quick starting point, load references/topic-map.md and jump to the closest section.
2. Search official BullMQ docs first
- Treat
docs.bullmq.ioas the source of truth for BullMQ. - Prefer pages under https://docs.bullmq.io/.
- Search with the user's exact terms plus focused BullMQ phrases such as
Queue,Worker,FlowProducer,repeat,limiter,sandboxed, orstalled. - When multiple pages are plausible, compare 2-3 candidate pages and pick the one that most directly answers the user's question.
- For API details, prefer the Guide and API Reference before answering from memory.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 102 lines · 86 tokens per session scan A 526fdc9228cc
bullmq-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (5 stars, last pushed 19d ago), licensed MIT. It adds 86 tokens to every session and 1,079 once invoked, about $0.0004 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
encore-go-cache
Cache data in Redis from Encore Go using cache.NewCluster and typed keyspaces from encore.dev/storage/cache. Type-safe key/value access with TTLs, atomic increments, and per-keyspace data shapes.
upstash-ratelimit-js
Rate limiting for serverless and edge apps with the @upstash/ratelimit TypeScript/JavaScript SDK backed by Upstash Redis. Use when adding a rate limiter or throttling to an API route, Next.js middleware, Vercel Edge, Cloudflare Workers, or any HTTP endpoint; returning 429 Too Many Requests; choosing between fixed…
laravel-async
Asynchronous and caching rules for Laravel — idempotent queued jobs with retries and backoff, domain events for side effects, queue separation and failure handling, deterministic cache keys with event-driven invalidation, and scheduled tasks that queue rather than block. Use when writing or reviewing jobs, events…
backend-patterns
Guides backend service architecture — layering, N+1 query prevention, caching, retries, rate limiting, and background job processing, in Go primarily and TypeScript/PHP where the pattern is language-agnostic. Use when structuring handler/service/repository layers, reviewing a service for N+1 queries, adding a cache in…
wp-plugin-performance
Performance guidelines for WordPress plugin development: database optimization, object caching, conditional asset loading, efficient hooks, HTTP requests, WP-Cron, AJAX/REST optimization, and common anti-patterns. Based on official WordPress Developer Resources and WP VIP documentation.
redis-caching
Redis caching, rate limiting, session storage, pub/sub, and production integration patterns for TypeScript, Next.js, NestJS, and Prisma applications. Use when adding cache-aside or write-through caching, rate limiting, session or lock storage, pub/sub fanout, or reviewing Redis key design and TTLs.