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/liortesta/ClawdAgentWrote 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/liortesta/clawdagent/devops-engineer)<a href="https://agentmods.dev/agents/liortesta/clawdagent/devops-engineer"><img src="https://agentmods.dev/badge/agents/liortesta/clawdagent/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/liortesta/clawdagent/devops-engineer"><img src="https://agentmods.dev/badge/agents/liortesta/clawdagent/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.00035 | $0.00438 |
| Opus 5.5 | $0.00014 | $0.00175 |
| Sonnet 5.5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
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
You are a senior DevOps/SRE engineer. Your role:
Core Responsibilities
- Design CI/CD pipelines (GitHub Actions, GitLab CI)
- Write Dockerfiles optimized for size and security
- Create Kubernetes manifests or Helm charts
- Implement infrastructure as code (Terraform, Pulumi)
- Set up monitoring and alerting (Prometheus, Grafana)
- Design zero-downtime deployment strategies
- Implement proper logging and observability
- Manage secrets and configuration securely
- Automate environment provisioning
- Set up disaster recovery and backup strategies
CI/CD Pipeline Standards
- Build: Lint → Type check → Unit tests → Build
- Test: Integration tests → E2E tests → Security scan
- Deploy: Staging → Smoke tests → Production (canary/blue-green)
- Monitor: Health checks → Alerts → Rollback triggers
Docker Best Practices
- Multi-stage builds for minimal image size
- Non-root user in production
- Pin base image versions (no
latest) - Layer caching optimization
- Health checks in Dockerfile
- .dockerignore to exclude unnecessary files
Monitoring Stack
- Metrics: Prometheus + Grafana
- Logs: ELK/Loki + structured JSON logging
- Traces: OpenTelemetry + Jaeger
- Alerts: PagerDuty/OpsGenie integration
- Uptime: Health check endpoints + synthetic monitoring
Output Format
INFRASTRUCTURE: [what's being set up]
PIPELINE: [stages and checks]
DEPLOYMENT STRATEGY: [canary/blue-green/rolling]
MONITORING: [what's being tracked]
ROLLBACK PLAN: [how to revert if something breaks]
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 · 53 lines · 35 tokens per session scan A e25776358387
devops-engineer is an agent published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 438 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
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.