job-queue

job-queue is a cursor rule for Cursor from golid-ai/golid. It costs 0 tokens per session (529 once invoked), scanned A, original, MIT.

Project rules for background jobs using a job queue, a system that stores work to run later, with Redis as an optional service.

In plain words
What is it for?
Use them when adding queued tasks, enqueueing work, creating task types, handling Redis configuration, or sending background emails in the queue package.
Why use it?
They keep the application working when Redis is not configured by using retrying background work instead, while requiring errors to be handled clearly.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/golid-ai/golid/job-queue
Clone the repo
git clone --depth 1 https://github.com/golid-ai/golid

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 529 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00529
Opus 5 $0.00000 $0.00264
Sonnet 5 $0.00000 $0.00106
Haiku 4.5 $0.00000 $0.00053

Measured 3d ago against content hash d87876da287c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

job-queue 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.

.cursor/rules/job-queue.mdc · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Job Queue Patterns

Thesis: The queue is opt-in via Redis. Every enqueue site checks IsConfigured() and falls back to retry-wrapped goroutines when Redis is absent.

Follow the established patterns in queue/queue.go, queue/tasks.go, and queue/handlers.go.

IsConfigured() Gate

The queue is opt-in via REDIS_URL. Every callsite that enqueues must check IsConfigured() and fall back to goroutines:

if h.queue.IsConfigured() {
    task, err := queue.NewSendVerificationEmail(email, token)
    if err != nil {
        logger.Error("failed to create task", slog.String("error", err.Error()))
    } else if err := h.queue.Enqueue(task); err != nil {
        logger.Error("failed to enqueue", slog.String("error", err.Error()))
    }
} else {
    go func() {
        if err := service.Retry(3, time.Second, func() error {
            return h.emailService.SendVerificationEmail(email, token)
        }); err != nil {
            logger.Error("failed to send email", slog.String("error", err.Error()))
        }
    }()
}

Critical: Use task, err := not task, _ :=. JSON marshal errors must be handled.

Adding a New Task Type

  1. Add a constant in queue/tasks.go: TypeMyNewTask = "domain:action"
  2. Add a payload struct and constructor: NewMyNewTask(args) (*asynq.Task, error)
  3. Add a handler method in queue/handlers.go with the same pattern
  4. Register in cmd/worker/main.go: mux.HandleFunc(queue.TypeMyNewTask, handler.HandleMyNewTask)
  5. Use the IsConfigured() gate pattern at the callsite

Worker

The worker process (cmd/worker/main.go) requires REDIS_URL. It shares the backend image with a different entrypoint. In Docker Compose, it uses the production profile.

Testing

  • Test task payload serialization round-trip in tasks_test.go
  • Test handler with mock EmailSender interface in handlers_test.go
  • Test IsConfigured() returns false with empty URL in queue_test.go
  • Test the goroutine fallback path in handler tests with mockQueue{configured: false}

Read the full file on GitHub · 56 lines

Changes

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.

  1. 3d ago First seen · 56 lines · 0 tokens per session scan A d87876da287c

Subscribe to this mod's changes

job-queue is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 529 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.