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 arjunprabhulal/devops-skills --skill argocd-operationsgit clone --depth 1 https://github.com/arjunprabhulal/devops-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/arjunprabhulal/devops-skills/argocd-operations)<a href="https://agentmods.dev/skills/arjunprabhulal/devops-skills/argocd-operations"><img src="https://agentmods.dev/badge/skills/arjunprabhulal/devops-skills/argocd-operations.svg" alt="Measured on agentmods" 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.00134 | $0.01413 |
| Opus 5 | $0.00067 | $0.00707 |
| Sonnet 5 | $0.00027 | $0.00283 |
| Haiku 4.5 | $0.00013 | $0.00141 |
Grade A, and why
argocd-operations 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 7d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Argo CD Operations
Argo CD is the reconciler that makes gitops real, but knowing the GitOps model doesn't tell you
how to structure hundreds of Applications, order their rollout, or figure out why one has been
"Progressing" for twenty minutes. Most Argo CD pain is operational, not conceptual: a bad sync wave
ordering, a health check that will never pass, or a manual sync habit that defeats the point of
having a reconciler at all.
Sync status tells you if the repo and cluster match; health status tells you if what's running actually works — treat them as two separate questions.
For stuck-sync states, sync waves, and the argocd app command reference, read
references/argocd-troubleshooting.md.
1. Manage many Applications with app-of-apps or ApplicationSets
Once you have more than a handful of Applications, don't create and wire each one by hand. A root "app of apps" Application whose only job is to manage child Application manifests gives you one commit to add a new service everywhere it belongs. ApplicationSets go further, generating Applications from a template plus a generator (a Git directory list, a cluster list, a pull request list) — use them when the same shape of Application needs to exist per-cluster or per-environment. Reserve hand-written Applications for the genuinely one-off cases.
Done when: onboarding a new service to an existing environment pattern is one small commit, not
a manual argocd app create.
2. Order dependencies explicitly with sync waves, don't hope
Argo CD syncs everything in an Application concurrently by default, which breaks when a Deployment
needs a CRD, ConfigMap, or Secret to exist first. Sync waves (argocd.argoproj.io/sync-wave
annotations) give you explicit, numbered ordering — negative waves for CRDs and namespaces, zero for
core resources, positive for anything that depends on them. Resource hooks (PreSync, PostSync,
SyncFail) exist for genuinely imperative steps like a database migration, but every hook is a small
admission that the desired state isn't fully declarative, so keep them rare and idempotent.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 104 lines · 134 tokens per session scan A 15799483cdc8
argocd-operations is a skill published in the GitHub repository arjunprabhulal/devops-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 134 tokens to every session and 1,413 once invoked, about $0.0007 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.
Other skills, from other repositories
google-cloud-slo-alert-configuration
Configures PromQL-based Service Level Objective (SLO) alerting policies for Google Cloud resources registered in App Hub or individually specified. Generates Terraform output. Use when the user asks to configure an SLO or Service Level Objective. Don't use for standard alerting policies.
cloud-build-basics
Teaches the fundamentals of Google Cloud Build (GCB). Covers core concepts, API enablement, console navigation to the Build History page, and the end-to-end workflow for creating and manually running a basic build trigger. Do not use for managing private pools or complex pipeline architectures.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
google-mobile-ads-android-migrate-to-next-gen
Migrates Android applications from the old, legacy Google Mobile Ads (GMA) SDK (com.google.android.gms:play-services-ads) to the new GMA Next-Gen SDK (com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk). Provides comprehensive mapping tables for imports, classes, and method signatures to help determine…
google-cloud-solution-guided-gke-ai-migration
Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl. Use when the user has an existing AI inference workload (on Cloud Run, the Gemini API, Gemini Enterprise Agent Platform, or a custom VM) and wants to move it to…
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…