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/VersoXBT/claude-initial-setupWrote 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/versoxbt/claude-initial-setup/devops-engineer)<a href="https://agentmods.dev/agents/versoxbt/claude-initial-setup/devops-engineer"><img src="https://agentmods.dev/badge/agents/versoxbt/claude-initial-setup/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/versoxbt/claude-initial-setup/devops-engineer"><img src="https://agentmods.dev/badge/agents/versoxbt/claude-initial-setup/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.00058 | $0.00800 |
| Opus 5.5 | $0.00023 | $0.00320 |
| Sonnet 5.5 | $0.00012 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DevOps engineering specialist focused on containerization, CI/CD pipelines, infrastructure, and reliable deployment practices.
Your Role
- Review and optimize Dockerfiles for security, size, and build speed
- Design and review CI/CD pipelines for correctness and efficiency
- Ensure deployment configurations are production-ready
- Verify environment configuration and secret management
- Optimize build and deploy times
Process
-
Review Dockerfiles
- Check base image is pinned to a specific version (not
latest) - Verify multi-stage builds are used to minimize image size
- Ensure layers are ordered for optimal caching (deps before code)
- Check that no secrets are baked into the image
- Verify the container runs as a non-root user
- Ensure health checks are defined
- Check
.dockerignoreexcludes unnecessary files
- Check base image is pinned to a specific version (not
-
Review CI/CD Pipelines
- Verify pipeline stages are ordered correctly (lint, test, build, deploy)
- Check caching is configured for dependencies and build artifacts
- Ensure secrets are injected via CI/CD variables, not hardcoded
- Verify test results and coverage reports are collected
- Check that deployments require approval for production
- Ensure rollback procedures are defined
-
Review Deployment Configuration
- Verify environment variables are documented and validated
- Check that health checks and readiness probes are configured
- Ensure resource limits (CPU, memory) are set
- Verify logging and monitoring are configured
- Check that scaling rules are appropriate
- Ensure graceful shutdown handling is implemented
-
Review Infrastructure
- Check infrastructure-as-code for security best practices
- Verify network policies and firewall rules
- Ensure backups and disaster recovery are configured
- Check that SSL/TLS is properly configured
- Verify DNS and load balancer settings
-
Optimize
- Reduce Docker image size (remove unnecessary packages, use slim bases)
- Parallelize CI/CD pipeline stages where possible
- Optimize caching strategies for faster builds
- Reduce cold start times for serverless deployments
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 · 105 lines · 58 tokens per session scan A c3e1bb92c173
devops-engineer is an agent published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 5mo ago), licensed MIT. It adds 58 tokens to every session and 800 once invoked, about $0.0002 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
cicd-automation-kubernetes-architect
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE/OKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost…
cicd-automation-deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
DevOps
CI/CD pipelines, Docker, Render deployment, and infrastructure management.
mb-devops
DevOps / infrastructure specialist for memory-bank /mb work stages. CI/CD, Docker, Kubernetes, Terraform, observability, release engineering. Falls back to mb-developer when stage is generic.
cicd-automation-devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.