Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/alivirgo/Major-AI-Skillsnpx agentmods add skills/alivirgo/major-ai-skills/fluxcdWrote 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/alivirgo/major-ai-skills/fluxcd)<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/fluxcd"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/fluxcd/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/alivirgo/major-ai-skills/fluxcd"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/fluxcd.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.02065 |
| Opus 5.5 | $0.00014 | $0.00826 |
| Sonnet 5.5 | $0.00007 | $0.00413 |
| Haiku 4.5 | $0.00004 | $0.00206 |
Grade A, and why
fluxcd 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.
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flux CD GitOps AI Skill Guide (Claude)
Overview & Engine Architecture
Flux reconciles Kubernetes from Git (or OCI) using composable controllers: source-controller (GitRepository, OCIRepository, HelmRepository, HelmChart), kustomize-controller, helm-controller, and optional image-reflector / image-automation. Unlike a single Application CR, Flux models sources and appliers as separate objects—debug by walking Ready conditions down the chain. Prefer digests in prod overlays; suspend before manual surgery on managed resources.
┌─────────────────────────────────────────────────────────────┐
│ Flux GitOps reconcile path │
│ │
│ GitRepository / OCIRepository / HelmRepository │
│ └── artifact fetch (auth Secret, ref, interval) │
│ │
│ Kustomization ──SSA apply──► cluster inventory + prune │
│ HelmRelease ──helm-ctrl──► HelmChart → release + wait │
│ │
│ Optional image automation │
│ ImageRepository → ImagePolicy → ImageUpdateAutomation→Git │
│ │
│ Debug: source Ready → applier Ready → workload health │
└─────────────────────────────────────────────────────────────┘
When to use / when not to
Use when
- Bootstrapping Flux (
flux bootstrap) and owning Git → cluster continuous delivery. - Authoring GitRepository + Kustomization or HelmRelease pipelines with prune and health checks.
- Debugging stalled reconciles, chart render errors, or image-automation tag bumps.
Do not use when
- The team wants a single Application UX with rich UI sync →
@argocdmay fit better (same GitOps idea, different model). - The task is building/pushing images → CI (
@github-actions); Flux consumes artifacts. - Someone asks to force-overwrite live cluster state without Git (and without suspend) → refuse; suspend → fix Git → resume.
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.
- 3d ago Changed · +78 lines · +11 tokens per session d79f8917a451
- 1mo ago Changed · -7 tokens per session a17d4995c463
- 1mo ago First seen · 148 lines · 32 tokens per session scan A 599367383183
fluxcd is a skill published in the GitHub repository alivirgo/Major-AI-Skills (2 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 2,065 once invoked, about $0.0001 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-05.
Other skills, from other repositories
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.
flux-controller-minor-releases
Run the upstream Flux controller minor release procedure for helm-controller, image-automation-controller, image-reflector-controller, kustomize-controller, notification-controller, source-controller, and source-watcher. Use when cutting a new controller minor release (vX.Y.0): creating the release series branch…
flux-controller-patch-releases
Run the upstream Flux controller patch release procedure for helm-controller, image-automation-controller, image-reflector-controller, kustomize-controller, notification-controller, source-controller, and source-watcher. Use when preparing a new controller patch release from a release series branch, drafting changelog…
commit-assisted-by
Add an Assisted-by: / git trailer to commits made during an AI-assisted coding session. Trigger on any git commit activity visible in the session — either commits you make yourself, or commits the user makes outside your tool calls that surface in the conversation — even without an explicit request. Also trigger when…
renovate
Generate renovate.json covering all dependency file types used in a repo, emit a GitHub Actions workflow that validates renovate.json on every PR, or generate a pre-commit hook for local validation.
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.