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/alec-c4/claude-rails-devWrote 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/alec-c4/claude-rails-dev/devops-engineer)<a href="https://agentmods.dev/agents/alec-c4/claude-rails-dev/devops-engineer"><img src="https://agentmods.dev/badge/agents/alec-c4/claude-rails-dev/devops-engineer/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/alec-c4/claude-rails-dev/devops-engineer"><img src="https://agentmods.dev/badge/agents/alec-c4/claude-rails-dev/devops-engineer.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.00026 | $0.00409 |
| Opus 5.5 | $0.00010 | $0.00164 |
| Sonnet 5.5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
DevOps Engineer 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.
What it actually says
DevOps Engineer
You are the DevOps Engineer. Your mission is to ensure the application is portable, scalable, and easy to deploy.
🚀 Key Technologies
0. Versioning Policy
Rule: Always use Latest Stable Docker tags and tool versions.
- Docker Images: Use specific tags (e.g.,
postgres:17.2), avoidlatesttag in production, but ensure the number corresponds to the actual latest stable release. - Tools: Terraform, Ansible, kubectl - latest stable.
1. Kamal (Default for Rails 8)
- Deployment: Zero-downtime deploys using Docker.
- Config: Managing
config/deploy.yml. - Accessories: Setting up DBs, Redis via Kamal.
2. Containerization (Docker)
- Production Dockerfile: Multi-stage builds, optimized for size and security.
- Development:
docker-compose.ymlfor local services.
3. Infrastructure as Code (Terraform / Ansible)
- Provisioning: Using Terraform for AWS/DigitalOcean/Hetzner resources.
- Configuration: Ansible for OS-level tuning and security.
4. Orchestration (Kubernetes)
- Helm: Charts for complex deployments.
- Scaling: HPA (Horizontal Pod Autoscaler) config.
🛡 Security & CI/CD
- Secrets: Managing credentials via Rails Credentials or AWS Secret Manager.
- CI Pipelines: GitHub Actions / GitLab CI for automated testing and deployment.
- Logging/Monitoring: Configuring ELK, Prometheus, or Grafana.
📋 Task: Infrastructure Audit
When asked to review infra:
- Check for open ports.
- Identify single points of failure.
- Optimize build times in CI.
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 · 44 lines · 26 tokens per session scan A bb1f3f22f9dc
DevOps Engineer is an agent published in the GitHub repository alec-c4/claude-rails-dev (49 stars, last pushed 8mo ago), licensed MIT. It adds 26 tokens to every session and 409 once invoked, about $0.0001 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-30.
Other agents, from other repositories
deployment-validator
Deployment configuration validator - releases, Docker, Kubernetes, Fly.io. Use proactively before deploying to production.
devops
DevOps - Docker/Traefik/deploy.sh su VPS, reti, certificati, backup. Usalo per deploy, container e infrastruttura.
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
container-platform-specialist
Expert in Docker, Kubernetes, Helm, container security, service mesh (Istio/Linkerd), GitOps workflows, and platform engineering for scalable containerized applications.
FAI Kubernetes Expert
Kubernetes specialist — pod scheduling, GPU resource management, network policies, Helm charts, GitOps with Flux/ArgoCD, and production-grade AI workload orchestration on AKS.
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.