agentmods.dev

gitops-lord

gitops-lord is a skill for Claude Code, Codex from m3taz-ahmed/ai-globals. It costs 41 tokens per session (1,163 once invoked), scanned A, original, MIT.

A guide to GitOps delivery for Kubernetes, where Git stores the intended deployment configuration and an automated system applies it to clusters. It covers ArgoCD, Helm, Flux, progressive releases, and multiple clusters.

In plain words
What is it for?
Use it to set up or review Kubernetes delivery, environment overlays, release validation, gradual rollouts, and multi-cluster application management.
Why use it?
Manual deployment commands can cause configuration drift and make changes harder to review or undo. Git-based deployment provides a recorded change history and allows rollback through Git.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 5repo yesterday A scan 41 tokens original MIT

Good fit Use it to set up or review Kubernetes delivery, environment overlays, release validation, gradual rollouts, and multi-cluster application management.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/m3taz-ahmed/ai-globals/gitops-lord
View source ↗ m3taz-ahmed/ai-globals
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.

Any agent
npx skills add m3taz-ahmed/ai-globals --skill gitops-lord
Clone the repo
git clone --depth 1 https://github.com/m3taz-ahmed/ai-globals

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for gitops-lord

README.md
[![agentmods](https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/gitops-lord/github.svg)](https://agentmods.dev/skills/m3taz-ahmed/ai-globals/gitops-lord)
Your own site
<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/gitops-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/gitops-lord/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.

agentmods 80×15 button for gitops-lord

Your own site · 80×15
<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/gitops-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/gitops-lord.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,163 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00041 $0.01163
Opus 5 $0.00020 $0.00581
Sonnet 5 $0.00008 $0.00233
Haiku 4.5 $0.00004 $0.00116

Measured 3d ago against content hash 9ff7b74dd140, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

gitops-lord 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.

skills/gitops-lord/SKILL.md · 71 lines

How it starts

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

GitOps Lord

[OBJ] Implement GitOps continuous delivery for Kubernetes using ArgoCD 3.5, Helm 4, and progressive delivery patterns.

Problem

Manual kubectl apply causes drift, lacks audit trail, and prevents rollback. GitOps makes Git the single source of truth — every deployment is a commit, every change is reviewable, every rollback is git revert. ArgoCD 3.5 (Aug 2026) adds impersonation, Source Hydrator, and ApplicationSet preview apps.

Rules

  1. [REQ] Git is the single source of truth. All manifests (Helm charts, Kustomize, raw YAML) live in Git. No kubectl apply outside of emergency break-glass procedures.
  2. [REQ] Use ArgoCD 3.5+ ApplicationSet for multi-environment deployments. Matrix generators (git × cluster) auto-generate apps per environment. Avoid manual Application creation.
  3. [REQ] Use Helm 4 charts (v3 is maintenance mode). helm template in CI for validation, helm install --dry-run before deploy. Never helm install without --atomic --timeout 5m.
  4. [REQ] Use Kustomize for environment overlays. base/ + overlays/dev|staging|prod/. Patch images, replicas, env vars per environment. Avoid duplicating manifests.
  5. [REQ] Enable selfHeal: true on production apps. Manual kubectl edit causes drift — ArgoCD auto-reverts to Git state.
  6. [REQ] Enable prune: true to remove resources deleted from Git. Without prune, deleted manifests leave orphaned resources.
  7. [REQ] Use ArgoCD impersonation (beta) for RBAC. Service accounts per team, least-privilege AppProject restrictions (repos, clusters, namespaces).
  8. [REQ] Use Source Hydrator (beta) for dry-source integrity verification. Validates manifests before sync, prevents malicious PRs from deploying.
  9. [REQ] Use Argo Rollouts for progressive delivery. Canary (5% → 25% → 50% → 100%) or Blue-Green. Auto-rollback on SLO violation (error rate, latency).
  10. [REQ] Use syncPolicy.automated for non-prod, manual sync for prod. Prod requires explicit argocd app sync after PR merge + review.
  11. [REQ] Use argocd app diff before sync to review changes. Use argocd app sync --dry-run to validate.
  12. [REQ] Secrets management. Use Sealed Secrets, External Secrets Operator, or SOPS — never commit plaintext secrets to Git. External Secrets syncs from Vault/AWS Secrets Manager.
  13. [REQ] Multi-cluster via ArgoCD. Register clusters with argocd cluster add. Use destinations in ApplicationSet for cluster routing. Single ArgoCD instance manages multiple clusters.
  14. [REQ] Use AppProject for isolation. Each team gets an AppProject with restricted sourceRepos, destinations (namespaces), and clusterResourceWhitelist.
  15. [PROHIBIT] Never disable selfHeal in production — manual edits cause drift.
  16. [PROHIBIT] Never use --force sync without understanding — deletes and recreates resources (downtime).
  17. [PROHIBIT] Never store secrets in Git plaintext — use Sealed Secrets or External Secrets Operator.

Read the full file on GitHub · 71 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 · 71 lines · 41 tokens per session scan A 9ff7b74dd140

Subscribe to this mod's changes

gitops-lord is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,163 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-09-09.

CI and CDDevOps and cloudGit and workflow
Related

Other skills, from other repositories

baby-sit

Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.

langchain-ai/open-swe · 30 tokens

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

atmos-hooks

Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.

cloudposse/atmos · 46 tokens

atmos-pro

Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.

cloudposse/atmos · 38 tokens

pr-watch

Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.

SethGammon/Citadel · 46 tokens

start-temps-cluster

Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…

gotempsh/temps · 204 tokens