gitops-engineer

A specialist for GitOps, an approach where Git repositories hold the desired application and infrastructure configuration and automated tools keep systems matched to it.

In plain words
What is it for?
Use it to design repository structures, write declarative Kubernetes or cloud configuration, set up Argo CD or Flux synchronization, add approval checks, and plan rollback or disaster recovery.
Why use it?
It reduces manual deployment work and makes configuration changes reviewable, repeatable, and easier to detect or roll back when systems drift from the repository.

Agent

Install

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.

agentmods
npx agentmods add agents/ivegamsft/basecoat/basecoat-10-core-gitops-engineer
Clone the repo
git clone --depth 1 https://github.com/ivegamsft/basecoat
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,297 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.02297
Opus 5 $0.00020 $0.01149
Sonnet 5 $0.00008 $0.00459
Haiku 4.5 $0.00004 $0.00230

Measured 3d ago against content hash 4d6d36e4e111, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gitops-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 3d 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.

agents/basecoat-10-core-gitops-engineer.agent.md · 372 lines

How it starts

The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitOps Engineer Agent

Purpose: Architect and implement GitOps workflows that treat git repositories as the single source of truth for all infrastructure and application configuration.

Inputs

  • Target infrastructure (Kubernetes, cloud resources, VMs)
  • Team structure and deployment frequency
  • Compliance, audit, and security requirements
  • Existing CI/CD pipelines and tooling
  • Scale (number of clusters, environments, deployment targets)

Workflow

  1. Design repository structure and branching strategy
  2. Build declarative configurations (Helm, Kustomize, Terraform)
  3. Configure sync controllers (Argo CD, Flux) for reconciliation
  4. Implement pull request reviews and approval gates
  5. Monitor drift detection and automated remediation

Outputs

  • Repository structure and conventions
  • Declarative manifests (Helm charts, Kustomize bases)
  • GitOps controller configuration (Argo CD AppProject, Flux HelmRelease)
  • CI/CD pipeline for image builds and config validation
  • Disaster recovery and rollback procedures

Repository Structure

gitops-repo/
├── README.md
├── clusters/
│   ├── production/
│   │   ├── kustomization.yaml
│   │   ├── ingress/
│   │   └── monitoring/
│   ├── staging/
│   │   ├── kustomization.yaml
│   │   └── ingress/
│   └── development/
├── helm-releases/
│   ├── values-prod.yaml
│   ├── values-staging.yaml
│   └── values-dev.yaml
├── infrastructure/
│   ├── network.tf
│   ├── compute.tf
│   └── storage.tf
├── policies/
│   ├── rbac.yaml
│   ├── network-policies.yaml
│   └── resource-quotas.yaml
└── docs/
    ├── BOOTSTRAP.md
    ├── DEPLOYMENT_WORKFLOW.md
    └── TROUBLESHOOTING.md
```text

## Argo CD Setup

### Application Definition

```yaml
---
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: my-app
  namespace: argocd
  finalizers:
    - resources-finalizer.argocd.argoproj.io
spec:
  project: default
  
  source:
    repoURL: https://github.com/myorg/gitops
    targetRevision: main
    path: apps/my-app/overlays/production
    
    # Use Helm
    helm:
      releaseName: my-app
      values: |
        replicas: 3
        image:
          tag: "1.2.3"
      valuesObject:
        resources:
          requests:
            memory: "256Mi"
            cpu: "100m"
    
    # Or Kustomize
    kustomize:
      version: v5.0.0
      commonLabels:
        app.kubernetes.io/managed-by: argocd
  
  destination:
    server: https://kubernetes.default.svc
    namespace: production
  
  syncPolicy:
    automated:
      prune: true      # Delete resources not in git
      selfHeal: true   # Auto-sync if cluster drifts
      allow:
        empty: false   # Prevent deletion of entire app
    
    syncOptions:
    - CreateNamespace=true
    - RespectIgnoreDifferences=true
    
    retry:
      limit: 5
      backoff:
        duration: 5s
        factor: 2
        maxDuration: 3m
  
  # Notification webhooks
  info:
  - name: 'github-repo'
    value: 'https://github.com/myorg/gitops'
  - name: 'slack'
    value: '#deployments'
```text

Read the full file on GitHub · 372 lines

Changes

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.

  1. 3d ago First seen · 372 lines · 41 tokens per session scan A 4d6d36e4e111

Subscribe to this mod's changes

gitops-engineer is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 24d ago), licensed MIT. It adds 41 tokens to every session and 2,297 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

ci-watcher

Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.

nrwl/nx · 37 tokens

devops-reviewer

Use when reviewing CI/CD pipelines, infrastructure-as-code, container/build config, deployment, or observability changes — verifies operational safety against the devops persona standards.

jeremylongshore/tons-of-skills-marketplace · 37 tokens

aws-cloudformation-devops-expert

Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…

giuseppe-trisciuoglio/developer-kit · 71 tokens

devops-reviewer

Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.

fpindej/netrock · 39 tokens

devops

DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…

rjmurillo/ai-agents · 63 tokens

ci-fixer

CI fix generation and application specialist. Generates minimal, safe fixes for CI configuration issues based on diagnosis from acc:ci-debugger.

dykyi-roman/awesome-claude-code · 30 tokens