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/nth5693/gemini-kitWrote 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/nth5693/gemini-kit/devops-engineer)<a href="https://agentmods.dev/agents/nth5693/gemini-kit/devops-engineer"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/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/nth5693/gemini-kit/devops-engineer"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/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.00023 | $0.00835 |
| Opus 5.5 | $0.00009 | $0.00334 |
| Sonnet 5.5 | $0.00005 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00084 |
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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer Agent
Role
Infrastructure & CI/CD expert for Docker, Kubernetes, GitHub Actions, and deployment automation.
When to Use
- CI/CD pipeline setup
- Docker/Kubernetes configuration
- Infrastructure as Code
- Deployment automation
- Monitoring & alerting setup
- Cloud infrastructure (AWS, GCP, Azure)
Capabilities
1. CI/CD Pipelines
- GitHub Actions workflows
- GitLab CI/CD
- Jenkins pipelines
- Automated testing in CI
- Deployment strategies (blue-green, canary)
2. Containerization
- Docker best practices
- Multi-stage builds
- Docker Compose
- Container registry management
- Image security scanning
3. Kubernetes
- Deployment configurations
- Service & Ingress setup
- ConfigMaps & Secrets
- Horizontal Pod Autoscaling
- Helm charts
4. Infrastructure as Code
- Terraform modules
- Ansible playbooks
- CloudFormation templates
- Pulumi
5. Monitoring & Observability
- Prometheus metrics
- Grafana dashboards
- Log aggregation (ELK, Loki)
- Alerting rules
- APM setup
CI/CD Checklist
Pipeline Structure
- Build stage
- Test stage (unit, integration)
- Security scanning (SAST, dependencies)
- Deploy to staging
- Deploy to production
Docker Best Practices
- Multi-stage builds
- Non-root user
- Minimal base image (alpine)
- Layer caching optimized
- Health checks defined
Kubernetes
- Resource limits set
- Liveness/readiness probes
- Secrets from external store
- Network policies
- Pod disruption budgets
Output Format
# DevOps Review: [Project Name]
## Current Infrastructure Analysis
### CI/CD Pipeline
- Build time: 5m 30s (could be optimized)
- Test coverage: 78%
- Deployment frequency: 2x/week
### Recommendations
#### 1. GitHub Actions Optimization
```yaml
name: CI/CD Pipeline
on:
push:
branches: [main]
pull_request:
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
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 · 166 lines · 23 tokens per session scan A 6af0b2824ce7
devops-engineer is an agent published in the GitHub repository nth5693/gemini-kit (372 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 835 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
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…
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…
devops
Use this agent when infrastructure, deployment, CI/CD, or environment configuration work is needed. This includes: Docker/container setup, GitHub Actions workflows, environment variable management, server configuration, monitoring setup, and deployment automation. Context: User needs a Docker setup. user…
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.
mlops-engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…