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.
git clone --depth 1 https://github.com/golid-ai/golidWrote 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/rules/golid-ai/golid/job-queue)<a href="https://agentmods.dev/rules/golid-ai/golid/job-queue"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/job-queue/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/rules/golid-ai/golid/job-queue"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/job-queue.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.00000 | $0.00529 |
| Opus 5.5 | $0.00000 | $0.00212 |
| Sonnet 5.5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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 1mo 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 — 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
- Add a constant in
queue/tasks.go:TypeMyNewTask = "domain:action" - Add a payload struct and constructor:
NewMyNewTask(args) (*asynq.Task, error) - Add a handler method in
queue/handlers.gowith the same pattern - Register in
cmd/worker/main.go:mux.HandleFunc(queue.TypeMyNewTask, handler.HandleMyNewTask) - 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
EmailSenderinterface inhandlers_test.go - Test
IsConfigured()returns false with empty URL inqueue_test.go - Test the goroutine fallback path in handler tests with
mockQueue{configured: false}
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.
- 1mo ago First seen · 56 lines · 0 tokens per session scan A d87876da287c
job-queue is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 3mo 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.
Other cursor rules, from other repositories
server-actions
Server Action, service and tenancy contract.
module-state-ownership
Module-state ownership & caches built from hot-reloading settings — How mutable module-scope state is owned here, and what caching anything derived from settings() obliges. Canonical file is .agents/rules/module-state-ownership.md.
performance-optimization
A set of Django performance rules for database queries, caching, background work, and static files. Django is a Python web framework.
using-archipy-adapters
Using and writing adapters in ArchiPy apps — extras, ports, test fakes, boundary errors.
services
Mono repo for Draft'n run source code.
spring-boot-redis
Spring Boot Redis contract for connection settings, RedisTemplate datastore access, Spring Cache with Redis, and Redis Pub/Sub.