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 agentmods add skills/yindia/rootcause/k8s-gitopsnpx skills add yindia/rootcause --skill k8s-gitopsgit clone --depth 1 https://github.com/yindia/rootcauseWhat 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 | $0.00000 | $0.02128 |
| Opus 5 | $0.00000 | $0.01064 |
| Sonnet 5 | $0.00000 | $0.00426 |
| Haiku 4.5 | $0.00000 | $0.00213 |
Grade A, and why
k8s-gitops 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: k8s-gitops
GitOps diagnostics and operational guidance for ArgoCD and Flux using RootCause MCP tool names only.
Scope
- Detect whether ArgoCD and/or Flux are installed.
- Diagnose sync and reconciliation health.
- Analyze drift and rollout failures.
- Correlate change timelines to incidents.
- Guide forced reconciliation workflows safely.
- Support environment promotion paths with verification.
Tooling Rule
- Use RootCause tool names only.
- Prefer
k8s.argocd_detectandk8s.flux_detectbefore deep diagnosis. - Use
k8s.diagnose_argocdandk8s.diagnose_fluxfor first-pass triage. - Use
k8s.describe,k8s.list,k8s.events, andk8s.events_timelinefor evidence detail.
Canonical Tool Set
k8s.argocd_detectk8s.diagnose_argocdk8s.flux_detectk8s.diagnose_fluxk8s.describek8s.listk8s.eventsk8s.events_timeline
Triggers
- gitops
- argocd
- flux
- out of sync
- app degraded
- reconciliation failed
- kustomization not ready
- helmrelease failed
- source fetch failed
- drift detected
- promotion blocked
- environment mismatch
- sync loop
Priority Rules
| Condition | First action | Why |
|---|---|---|
| Unknown platform | Run k8s.argocd_detect and k8s.flux_detect |
Fast platform fingerprint |
| ArgoCD suspected issue | Run k8s.diagnose_argocd |
Consolidates sync + health + events |
| Flux suspected issue | Run k8s.diagnose_flux |
Consolidates source + reconcile signals |
| Need object-level reason | Run k8s.describe |
Full status/conditions/events |
| Need inventory | Run k8s.list |
Lists all relevant CRs |
| Need chronology | Run k8s.events_timeline |
Aligns failure to changes |
ArgoCD Application States
| Sync status | Health status | Interpretation | Action |
|---|---|---|---|
| Synced | Healthy | Desired and live match | Monitor only |
| Synced | Degraded | Live matches desired but app unhealthy | Inspect workload failures |
| OutOfSync | Healthy | Drift exists but app currently serving | Investigate drift source |
| OutOfSync | Degraded | Drift plus unhealthy app | Prioritize immediate remediation |
| Unknown | Unknown | Controller cannot evaluate | Check controller availability and access |
| Synced | Progressing | Deployment in-flight | Validate rollout convergence |
What ships with it
2 files 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.
- 2d ago First seen · 249 lines · 0 tokens per session scan A 587ad69eee7b
k8s-gitops is a skill published in the GitHub repository yindia/rootcause (42 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,128 tokens. 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 skills, from other repositories
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.
test-radar
Use when building and testing Radar changes with the repository's real-instance smoke-test workflow.
visual-test
Use when visually testing Radar UI changes against a real Kubernetes cluster with Playwright screenshots.
release-chart
Cut and publish a new release of the Zabbix Helm chart in this repository, following the versioning rules and maintainer release process documented in CONTRIBUTING.md and CLAUDE.md (bump Chart.yaml/artifacthub-pkg.yml/values.yaml, regenerate docs, tag the release so CI publishes it). Trigger on requests like "release…
helm
Skill "helm" from chaterm/terminal-skills, covering helm 包管理, 概述, 基础命令, 仓库管理 and 添加仓库.
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.