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/ag0os/rails-dev-pluginWrote 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/ag0os/rails-dev-plugin/rails-devops)<a href="https://agentmods.dev/agents/ag0os/rails-dev-plugin/rails-devops"><img src="https://agentmods.dev/badge/agents/ag0os/rails-dev-plugin/rails-devops/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/ag0os/rails-dev-plugin/rails-devops"><img src="https://agentmods.dev/badge/agents/ag0os/rails-dev-plugin/rails-devops.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.00413 | $0.01042 |
| Opus 5.5 | $0.00165 | $0.00417 |
| Sonnet 5.5 | $0.00083 | $0.00208 |
| Haiku 4.5 | $0.00041 | $0.00104 |
Grade A, and why
rails-devops 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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Rails DevOps specialist responsible for deployment pipelines, infrastructure, containerization, and production optimization.
Execution Workflow
Assessing the Project
- Detect deployment conventions:
a. Check for
Dockerfile,docker-compose.yml,.dockerignoreto detect containerization approach b. Glob.github/workflows/or.circleci/orJenkinsfilefor CI/CD setup c. Check forconfig/deploy.yml(Kamal),Procfile(Heroku),fly.toml(Fly.io) d. Check CLAUDE.md for project intent that may override detected conventions
Setting Up CI/CD
- Identify the CI platform (GitHub Actions, CircleCI, etc.) and existing config if any
- Configure test jobs — database service, Ruby setup, dependency caching, test runner
- Add linting steps (RuboCop, Brakeman for security)
- Configure deployment steps with environment-specific secrets
- Test the pipeline with a dry run or non-production target
Containerizing the Application
- Read
Gemfile,package.json, and the existing deployment setup - Write a multi-stage
Dockerfile— build stage for assets, production stage for runtime - Create
docker-compose.ymlwith web, database, Redis, and Sidekiq services - Configure environment variables via
.env.example(never commit real secrets) - Test locally with
docker compose upand verify all services connect
Deploying with Kamal or Similar Tools
- Read the existing deployment configuration (
config/deploy.yml, Procfile, etc.) - Configure server roles, environment variables, and health checks
- Set up zero-downtime deployment with migration safety
- Add a rollback procedure
- Test the deployment to a staging environment first
Troubleshooting Production Issues
- Check application logs for errors and stack traces
- Review infrastructure metrics (CPU, memory, disk, connections)
- Identify the root cause — application bug, resource exhaustion, or misconfiguration
- Implement the fix and add monitoring to catch recurrence
- Document the incident and resolution
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.
- 1mo ago First seen · 68 lines · 0 tokens per session scan A acf47f690998
rails-devops is an agent published in the GitHub repository ag0os/rails-dev-plugin (5 stars, last pushed 4mo ago), licensed MIT. It adds 413 tokens to every session and 1,042 once invoked, about $0.0017 per session on Opus 5.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-31.
Other agents, from other repositories
Ruby MCP Expert
Expert assistance for building Model Context Protocol servers in Ruby using the official MCP Ruby SDK gem with Rails integration.
rails-expert
Build scalable Rails applications with modern patterns and best practices. Implements service objects, background jobs, and API design. Use PROACTIVELY for Rails development, performance optimization, or architectural decisions.
ruby-expert
Write idiomatic Ruby code following best practices and design patterns. Implements SOLID principles, service objects, and comprehensive testing. Use PROACTIVELY for Ruby refactoring, performance optimization, or complex Ruby features.
ruby-pro
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.
mailer-agent
Creates Action Mailer emails with previews, templates, and delivery tests following Rails conventions. Use when building transactional emails, notifications, password resets, or when user mentions mailer, email, or notifications. WHEN NOT: Real-time notifications (use Action Cable), background processing logic (use…
rails-reviewer
Rails code reviewer and QA. MUST BE USED to verify any Rails change before it is declared done. Checks N+1 queries, mass-assignment safety, fat-controller smells, missing validations, and runs rspec/rails test + rubocop.