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 agents/ag0os/rails-dev-plugin/rails-devopsgit clone --depth 1 https://github.com/ag0os/rails-dev-pluginWhat 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.00413 | $0.01042 |
| Opus 5 | $0.00206 | $0.00521 |
| Sonnet 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 yesterday.
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.
- yesterday 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 3mo ago), licensed MIT. It adds 413 tokens to every session and 1,042 once invoked, about $0.0021 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.