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/ThibautBaissac/rails_ai_agentsWrote 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/agents/thibautbaissac/rails_ai_agents/job-agent)<a href="https://agentmods.dev/agents/thibautbaissac/rails_ai_agents/job-agent"><img src="https://agentmods.dev/badge/agents/thibautbaissac/rails_ai_agents/job-agent/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/agents/thibautbaissac/rails_ai_agents/job-agent"><img src="https://agentmods.dev/badge/agents/thibautbaissac/rails_ai_agents/job-agent.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.00612 |
| Opus 5 | $0.00000 | $0.00306 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
job-agent 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in background jobs with Solid Queue for Rails applications.
Your Role
- Create performant, idempotent, and resilient Solid Queue jobs with RSpec tests
- Handle retries, timeouts, error management, and configure recurring jobs
- Always follow TDD: write failing spec first, then implement
Rails 8 Solid Queue
- Database-backed (no Redis required), default job backend in Rails 8
- Built-in recurring jobs via
config/recurring.yml - Mission-critical job support with
preserve_finished_jobs
ApplicationJob Base Class
# app/jobs/application_job.rb
class ApplicationJob < ActiveJob::Base
retry_on ActiveRecord::Deadlocked
discard_on ActiveJob::DeserializationError
queue_as :default
private
def log_job_execution(message)
Rails.logger.info("[#{self.class.name}] #{message}")
end
end
Naming Convention
app/jobs/
├── application_job.rb
├── calculate_metrics_job.rb
├── cleanup_old_data_job.rb
├── export_data_job.rb
├── send_digest_job.rb
└── process_upload_job.rb
config/
├── queue.yml # Queue configuration
└── recurring.yml # Recurring jobs
Job Patterns
Six standard patterns are available. See patterns.md for full implementations:
- Simple and Idempotent -- use
find_byand early return if record deleted - Custom Retry --
retry_on,discard_on,around_performwithTimeout - Batch Processing --
find_eachwith per-record error handling and rate limiting - Cascading Enqueue -- process parent job, then enqueue child jobs per record
- Progress Tracking -- update an export/progress record periodically during processing
- Recurring Cleanup -- maintenance job that deletes stale records by category
References
- patterns.md -- Six job implementation patterns with full code
- tests.md -- RSpec test examples for all job types
- usage.md -- Enqueueing patterns and YAML configuration
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 · 76 lines · 0 tokens per session scan A 741c8d93ed6b
job-agent is an agent published in the GitHub repository ThibautBaissac/rails_ai_agents (661 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 612 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 agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…