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 sandeepmvl/rails-skills --skill 07-solid-queue-and-sidekiqgit clone --depth 1 https://github.com/sandeepmvl/rails-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/sandeepmvl/rails-skills/07-solid-queue-and-sidekiq)<a href="https://agentmods.dev/skills/sandeepmvl/rails-skills/07-solid-queue-and-sidekiq"><img src="https://agentmods.dev/badge/skills/sandeepmvl/rails-skills/07-solid-queue-and-sidekiq/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/sandeepmvl/rails-skills/07-solid-queue-and-sidekiq"><img src="https://agentmods.dev/badge/skills/sandeepmvl/rails-skills/07-solid-queue-and-sidekiq.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.00140 | $0.03959 |
| Opus 5 | $0.00070 | $0.01980 |
| Sonnet 5 | $0.00028 | $0.00792 |
| Haiku 4.5 | $0.00014 | $0.00396 |
Grade A, and why
solid-queue-and-sidekiq 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solid Queue and Sidekiq
Decide which job backend to run, design jobs that retry safely, and stop putting things in background jobs that don't belong there. AI agents over-async by reflex (
Job.perform_latereverywhere) and under-think idempotency (which is where retries bite).
Why this matters
Background jobs are infrastructure. Pick wrong and you're running Redis you didn't need, or your DB is melting under polling. Pick right and they're invisible until they fail — and when they fail, the question is always: "is it safe to retry?"
The opinion
Greenfield Rails 8: Solid Queue, no Redis. Existing Sidekiq investment or specific Sidekiq features needed (Pro/Enterprise rate limiting, batches): keep Sidekiq. Every job: idempotent by design. Retries with exponential backoff. External effects guarded by lookup-before-write.
after_commitenqueue, neverafter_save.
Counter-positions:
- GoodJob — Postgres-only, mature, supports cron. Solid Queue covers ~all its features now and ships with Rails 8.
- delayed_job — fine for tiny apps, dated for everything else.
- Resque — historical, don't pick for new work.
Decision matrix — which backend
| Concern | Solid Queue | Sidekiq |
|---|---|---|
| Default for Rails 8 greenfield | Yes | — |
| Requires Redis | No (uses your DB) | Yes |
| Throughput | Moderate (DB-polling) | High (Redis-driven) |
FOR UPDATE SKIP LOCKED requirement |
PG 9.5+, MySQL 8+ | — |
| Concurrency controls | Yes (but pricey overhead at scale) | Yes (built-in + Pro batches) |
| Recurring jobs | recurring.yml built-in |
sidekiq-cron (or sidekiq-scheduler) |
| Web dashboard | Mission Control built-in | Sidekiq web UI |
| Cost | Free | OSS free; Pro/Enterprise paid (rate limiting, batches, unique jobs) |
| When to pick | Default Rails 8 — no extra infra | Already running Redis, OR need >5k jobs/sec, OR need Pro features |
For migrations from Sidekiq to Solid Queue: both speak Active Job, so application code doesn't change. Switch config.active_job.queue_adapter. Drain Sidekiq queues, then cut over. Plan for Sidekiq-specific gems (sidekiq-cron, sidekiq-throttled, sidekiq-unique-jobs) to need replacements.
What ships with it
1 file 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.
- 9d ago First seen · 401 lines · 140 tokens per session scan A 1804a648e29d
solid-queue-and-sidekiq is a skill published in the GitHub repository sandeepmvl/rails-skills (21 stars, last pushed 3mo ago), licensed MIT. It adds 140 tokens to every session and 3,959 once invoked, about $0.0007 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
rails-expert
Rails 7+ specialist that optimizes Active Record queries with includes/eagerload, implements Turbo Frames and Turbo Streams for partial page updates, configures Action Cable for WebSocket connections, sets up Sidekiq workers for background job processing, and writes comprehensive RSpec test suites. Use when building…
new
Create a new project to start development quickly.
rails-conventions
Rootstrap Rails conventions. Use when writing, reviewing, or editing any Rails code — controllers, models, migrations, routes, views, mailers, initializers, locale files, or Rails config. Covers routing, ActiveRecord, migrations, i18n, time zones, mailers, assets, Bundler groups, and logging.
ruby-rails
Conventions and best practices for building web applications with Ruby on Rails. Use when scaffolding Rails apps or generators, designing ActiveRecord models and migrations, wiring up Hotwire/Turbo/Stimulus interactivity, setting up background jobs or caching, or writing RSpec/Minitest coverage for Rails code.
ruby-expert
Expert-level Ruby development with Rails, modern features, testing, and best practices. Use when the user mentions Ruby on Rails, RSpec, gem, Sinatra, or metaprogramming, or when the task involves Ruby 3+ Features, Object-Oriented, Functional Features, or Pattern Matching.
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…