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/fluxcd/agent-skillsnpx agentmods add skills/fluxcd/agent-skills/gitops-knowledgeWrote 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/fluxcd/agent-skills/gitops-knowledge)<a href="https://agentmods.dev/skills/fluxcd/agent-skills/gitops-knowledge"><img src="https://agentmods.dev/badge/skills/fluxcd/agent-skills/gitops-knowledge/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/fluxcd/agent-skills/gitops-knowledge"><img src="https://agentmods.dev/badge/skills/fluxcd/agent-skills/gitops-knowledge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 119 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00128 | $0.03811 |
| Opus 5.5 | $0.00051 | $0.01524 |
| Sonnet 5.5 | $0.00026 | $0.00762 |
| Haiku 4.5 | $0.00013 | $0.00381 |
Grade A, and why
gitops-knowledge 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 1mo 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flux CD Knowledge Base
You are an expert on Flux CD, the GitOps toolkit for Kubernetes. Use this knowledge base to answer questions accurately, generate correct YAML manifests, and explain Flux concepts.
Rules:
- Always use the exact apiVersion/kind combinations from the CRD table below. Never invent API versions.
- Before generating YAML for any CRD, verify field names, types, enums and required fields against its field index in
assets/schemas/. Each line is<dotted.path> <type> [(required)] [enum=a|b] [default=x] [pattern="..."] [min=N max=N] # description(arrays aspath[], maps as<map[string]T>). Grep a path prefix to list a subtree (grep '^spec\.chart\.' assets/schemas/helmrelease-helm-v2.fields.txt) or a field name to find where it lives. Mutual-exclusivity and other CEL rules are enforced byflux schema validate. - When a question requires detail beyond this file, load the relevant reference file from
references/. - When working inside a GitOps repository, inventory the layout with
flux schema discoverbefore placing files, and after writing manifests validate them withflux schema validate— fix and re-run until clean. Loadreferences/flux-cli.mdfor the full CLI workflow, local rendering, and overlay debugging. If the tools aren't installed, skip validation and say so. - Prefer Flux Operator (FluxInstance) for cluster setup. Do not reference
flux bootstrapor legacygotk-*files.
What is Flux
Flux is a set of Kubernetes controllers that implement GitOps: Git or OCI registries are the
source of truth, and Flux continuously reconciles that desired state with the cluster. Sources
poll at their interval and produce versioned artifacts; appliers (kustomize-controller,
helm-controller) build and server-side apply new revisions, detect drift and self-heal;
notification-controller reports status externally. Flux Operator manages the Flux
installation declaratively through a FluxInstance custom resource (install, configuration,
upgrades, lifecycle of all controllers); only one FluxInstance named flux can exist per cluster.
What ships with it
36 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.
- assets/schemas/alert-notification-v1beta3.fields.txt 2.6 KB
- assets/schemas/artifactgenerator-source-v1beta1.fields.txt 7.4 KB
- assets/schemas/bucket-source-v1.fields.txt 8.0 KB
- assets/schemas/externalartifact-source-v1.fields.txt 3.8 KB
- assets/schemas/fluxinstance-fluxcd-v1.fields.txt 14 KB
- assets/schemas/fluxreport-fluxcd-v1.fields.txt 5.4 KB
- assets/schemas/gitrepository-source-v1.fields.txt 11 KB
- assets/schemas/helmchart-source-v1.fields.txt 7.4 KB
- assets/schemas/helmrelease-helm-v2.fields.txt 39 KB
- assets/schemas/helmrepository-source-v1.fields.txt 7.4 KB
- assets/schemas/imagepolicy-image-v1.fields.txt 5.6 KB
- assets/schemas/imagerepository-image-v1.fields.txt 6.2 KB
- assets/schemas/imageupdateautomation-image-v1.fields.txt 10 KB
- assets/schemas/kustomization-kustomize-v1.fields.txt 20 KB
- assets/schemas/ocirepository-source-v1.fields.txt 9.8 KB
- assets/schemas/provider-notification-v1beta3.fields.txt 3.9 KB
- assets/schemas/receiver-notification-v1.fields.txt 8.0 KB
- assets/schemas/resourceset-fluxcd-v1.fields.txt 11 KB
- assets/schemas/resourcesetinputprovider-fluxcd-v1.fields.txt 10 KB
- evals/evals.json 34 KB
- references/best-practices.md 6.3 KB
- references/flux-cli.md 10 KB
- references/flux-operator.md 10 KB
- references/gitless-gitops.md 15 KB
- references/gitless-image-automation.md 7.7 KB
- references/helmrelease.md 10 KB
- references/image-automation.md 10 KB
- references/kustomization.md 12 KB
- references/mcp-server.md 7.4 KB
- references/monorepo-delivery.md 25 KB
- references/notifications.md 12 KB
- references/repo-patterns.md 14 KB
- references/resourcesets.md 36 KB
- references/sources.md 15 KB
- references/terraform-bootstrap.md 16 KB
- references/web-ui.md 9.8 KB
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.
- 1mo ago First seen · 292 lines · 128 tokens per session scan A 7be56232f0fd
gitops-knowledge is a skill published in the GitHub repository fluxcd/agent-skills (233 stars, last pushed today), licensed Apache-2.0. It adds 128 tokens to every session and 3,811 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
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…
gke-ai-troubleshooting-tpu-partition-overlap
Diagnose and resolve GKE TPU slice creation failures (SliceCreationFailed) caused by partition overlap conflicts where requested TPU partitions or their nodes are already used by another slice or JobSet. Use when diagnosing GKE TPU slice creation failures with SliceCreationFailed partition or node conflicts. Don't use…
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).