Borrowing it
Nothing to install: this file belongs to levifig/rails-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/levifig/rails-instructions/main/.github/instructions/rails-background-jobs.instructions.mdgit clone --depth 1 https://github.com/levifig/rails-instructionsWrote 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/instructions/levifig/rails-instructions/rails-background-jobs)<a href="https://agentmods.dev/instructions/levifig/rails-instructions/rails-background-jobs"><img src="https://agentmods.dev/badge/instructions/levifig/rails-instructions/rails-background-jobs/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/instructions/levifig/rails-instructions/rails-background-jobs"><img src="https://agentmods.dev/badge/instructions/levifig/rails-instructions/rails-background-jobs.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.01026 | $0.01026 |
| Opus 5 | $0.00513 | $0.00513 |
| Sonnet 5 | $0.00205 | $0.00205 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
rails-instructions rails-background-jobs.instructions.md 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 10d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Background Jobs Guide (Solid Queue)
Core Philosophy
- Use database-backed queuing for simplicity and reliability
- Avoid external dependencies like Redis when possible
- Design jobs to be idempotent and retryable
- Keep background processing simple and focused
- Leverage Rails' built-in Active Job framework
Solid Queue Principles
- Database-backed job storage using FOR UPDATE SKIP LOCKED
- No external dependencies required for basic operation
- Built-in support for priorities, concurrency limits, and recurring jobs
- Seamless integration with Active Job interface
- Production-ready performance with PostgreSQL or MySQL
Configuration Strategy
- Use separate database for queue in high-volume production environments
- Configure workers based on job priorities and server resources
- Set appropriate polling intervals for job urgency
- Design thread counts based on database connection limits
- Monitor queue depth and processing times
Queue Organization
- Design queues based on priority and processing requirements
- Use semantic queue names that indicate purpose
- Configure dedicated workers for high-priority queues
- Set appropriate concurrency limits per queue type
- Use wildcards sparingly - prefer explicit queue names
Job Design Principles
- Make all jobs idempotent - safe to run multiple times
- Keep jobs small and focused on single tasks
- Pass simple arguments - prefer IDs over objects
- Design for eventual consistency
- Handle failures gracefully with proper error reporting
Error Handling Strategy
- Configure retry behavior based on job importance
- Use exponential backoff for transient failures
- Discard jobs that cannot succeed after retries
- Log errors with sufficient context for debugging
- Monitor failed job patterns for system issues
Concurrency Controls
- Use
limits_concurrencyto prevent resource exhaustion - Define concurrency keys based on resource constraints
- Set appropriate duration for concurrency locks
- Group related jobs with concurrency controls
- Monitor for concurrency bottlenecks
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.
- 10d ago First seen · 177 lines · 1,026 tokens per session scan A 426b8ad3b658
rails-instructions rails-background-jobs.instructions.md is an instructions file published in the GitHub repository levifig/rails-instructions (55 stars, last pushed 1y ago), licensed MIT. It adds 1,026 tokens to every session, about $0.0051 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 instructions, from other repositories
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.