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.
npx skills add j4flmao/agent-skills --skill gitopsgit clone --depth 1 https://github.com/j4flmao/agent-skillsWrote 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/skills/j4flmao/agent-skills/gitops)<a href="https://agentmods.dev/skills/j4flmao/agent-skills/gitops"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/gitops/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/skills/j4flmao/agent-skills/gitops"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/gitops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00161 | $0.01865 |
| Opus 5.5 | $0.00064 | $0.00746 |
| Sonnet 5.5 | $0.00032 | $0.00373 |
| Haiku 4.5 | $0.00016 | $0.00186 |
Grade A, and why
cloud-native-argocd-reconciliation 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 2d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Argo CD Reconciliation and Drift Detection
Purpose
Argo CD continuously compares manifests rendered from Git with live objects and reports Synced/OutOfSync and health. Knowing which component does what — and how the diff is computed — is what lets you fix permanent OutOfSync, slow reconciliation, and unsafe auto-sync.
Agent Protocol
Trigger
"argocd reconciliation", "drift detection", "OutOfSync", "argocd diff", "ignoreDifferences", "server-side diff", "sync waves", "refresh vs sync", "application controller".
Input Context
- Argo CD version, number of Applications/clusters.
- The resource and field that shows a diff; sync options in use.
- Mutating webhooks/operators that modify the resource (HPA, Istio injection, cert-manager, defaulting).
Output Artifact
Diagnosis plus Application/ConfigMap changes. No file unless requested.
Response Format
Symptom: {OutOfSync on <kind>/<field> | slow refresh | sync failure}
Cause: {defaulted field|mutating webhook|controller-owned field|generator drift}
Fix: {ignoreDifferences|ServerSideDiff|RespectIgnoreDifferences|manifest change}
Snippet: {YAML}
Completion Criteria
- Root cause identified as a specific field and its writer.
- Fix scoped to that field (no blanket ignores of whole resources).
Components
| Component | Role |
|---|---|
argocd-repo-server |
Clones Git/OCI/Helm repos and renders manifests (Helm template, Kustomize build, plain YAML, config management plugins). Results cached (in Redis) by revision + parameters. |
argocd-application-controller |
Keeps a per-cluster in-memory cache of live resources built with Kubernetes watches; compares rendered manifests to live state; runs syncs; computes health. Sharded across replicas by cluster. |
argocd-server |
API/UI; triggers refresh/sync. |
| Redis | Cache for rendered manifests and app-state snapshots shown in the UI — not the source of the live-state cache. |
argocd-applicationset-controller |
Generates Applications from generators. |
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.
- 2d ago Changed · +98 lines · +138 tokens per session c1a945f7ef4a
- 1mo ago First seen · 43 lines · 23 tokens per session scan A c01f51f5a99a
cloud-native-argocd-reconciliation is a skill published in the GitHub repository j4flmao/agent-skills (35 stars, last pushed yesterday), licensed MIT. It adds 161 tokens to every session and 1,865 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
argocd
Operate Argo CD GitOps with AppProjects, safe automated sync/prune, and RespectIgnoreDifferences—debug OutOfSync/Degraded without kubectl drift that fights the controller.
gitops-workflows
GitOps workflows and patterns using ArgoCD and Flux for declarative Kubernetes deployments. Use when implementing CI/CD for Kubernetes, managing multi-environment deployments, or adopting declarative infrastructure practices.
Triage Argo CD App OutOfSync
Identify why an Argo CD application is OutOfSync and resolve safely.
argocd
Argo CD GitOps continuous delivery reference for Kubernetes. Covers installation, application management, Helm/Kustomize sources, App-of-Apps pattern, ApplicationSet generators, sync waves, progressive delivery, RBAC, SSO, and secrets.
bex-cli
Installs and uses the bex CLI for deploys, logs, SSH, psql, Blueprint validation, and automation. Use when the user needs to run bex CLI commands, script deploys in CI/CD, authenticate with an API key, query services non-interactively, or troubleshoot CLI auth issues. Trigger terms: bex CLI, bex login, bex deploys…
argocd-expert
Expert-level ArgoCD GitOps deployment, application management, sync strategies, and production operations. Use when the user mentions GitOps, Kubernetes, continuous deployment, declarative, or automation, or when the task involves ArgoCD Architecture, Application CRD, AppProject, or ApplicationSet.