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/fluxcd/agent-skills/gitops-knowledgenpx skills add fluxcd/agent-skills --skill gitops-knowledgegit clone --depth 1 https://github.com/fluxcd/agent-skillsWhat 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.00128 | $0.03811 |
| Opus 5 | $0.00064 | $0.01906 |
| Sonnet 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 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 — 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.
- 2d 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 (214 stars, last pushed 7d ago), licensed Apache-2.0. It adds 128 tokens to every session and 3,811 once invoked, about $0.0006 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-30.
Other skills, from other repositories
go-check
Run go vet to analyze Go source code for suspicious constructs.
shell-check
Run shellcheck to lint shell scripts for common issues and best practices.
yaml-check
Run yq to validate and lint YAML files for correctness.
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.