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 agentmods add rules/romkey/i2c-directory/sidekiq-queuesgit clone --depth 1 https://github.com/romkey/I2C-DirectoryWrote 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/romkey/i2c-directory/sidekiq-queues)<a href="https://agentmods.dev/rules/romkey/i2c-directory/sidekiq-queues"><img src="https://agentmods.dev/badge/rules/romkey/i2c-directory/sidekiq-queues.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 | $0.00000 | $0.00268 |
| Opus 5 | $0.00000 | $0.00134 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
sidekiq-queues 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.
What it actually says
Sidekiq Queue Configuration
No ActiveJob queue_name_prefix
NEVER add config.active_job.queue_name_prefix in any environment config.
This app uses a dedicated Redis instance — queue namespacing is unnecessary.
# BAD — causes double-prefixed queues with sidekiq-cron
config.active_job.queue_name_prefix = "member_manager_production"
# GOOD — no prefix, plain queue names
config.active_job.queue_adapter = :sidekiq
# (no queue_name_prefix line at all)
Sidekiq queue list
In config/initializers/sidekiq.rb, use plain queue names only:
# BAD
config.queues = ["#{prefix}_default", "#{prefix}_mailers"]
# GOOD
config.queues = %w[default mailers]
sidekiq-cron jobs
All cron jobs must use active_job: true. Do not set an explicit queue:
on cron entries — let the job class's queue_as determine the queue.
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.
- 3d ago First seen · 39 lines · 0 tokens per session scan A 37f69e85beaf
sidekiq-queues is a cursor rule published in the GitHub repository romkey/I2C-Directory (11 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 268 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
cursorrules
🚨 ABSOLUTELY FORBIDDEN: Direct python/python3 execution.
compile-after-changes
After significant code changes, build with pio run to confirm the firmware compiles.
arduino-skills
Route Arduino and embedded work through the shared skills tree with board-aware and evidence-aware constraints.
cursorrules
This is an embedded systems project for the ESP32-S3-Touch-LCD-1.85C device. All development must strictly follow the project constitution located at .cursor/rules.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.