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/levifig/rails-instructions/background-jobsgit 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/rules/levifig/rails-instructions/background-jobs)<a href="https://agentmods.dev/rules/levifig/rails-instructions/background-jobs"><img src="https://agentmods.dev/badge/rules/levifig/rails-instructions/background-jobs.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.01030 |
| Opus 5 | $0.00000 | $0.00515 |
| Sonnet 5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
background-jobs 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 5d 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 — 157 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.
- 5d ago First seen · 157 lines · 0 tokens per session scan A 631bb6dc94a1
background-jobs is a cursor rule published in the GitHub repository levifig/rails-instructions (54 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,030 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
pytest-integration-tests
Below is an example test. Notice the following.
python-app
Cursor rule "python-app" from iloveitaly/llm-ide-rules, covering python app, factories and database & orm.
react
Cursor rule "react" from iloveitaly/llm-ide-rules, covering react, mock data, react hook form and styling.
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
pytest-tests
Below is an example test, you'll notice the following.