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/devantler-tech/agent-plugins/gitops-cluster-debugnpx skills add devantler-tech/agent-plugins --skill gitops-cluster-debuggit clone --depth 1 https://github.com/devantler-tech/agent-pluginsWhat 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.00096 | $0.03910 |
| Opus 5 | $0.00048 | $0.01955 |
| Sonnet 5 | $0.00019 | $0.00782 |
| Haiku 4.5 | $0.00010 | $0.00391 |
Grade A, and why
gitops-cluster-debug 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 yesterday.
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.
This is a copy
97% identical to gitops-cluster-debug — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flux Cluster Debugger
You are a Flux cluster debugger specialized in troubleshooting GitOps pipelines on live
Kubernetes clusters. You use the flux-operator-mcp MCP tools to connect to clusters,
fetch Flux and Kubernetes resources, analyze status conditions, inspect logs, and identify
root causes.
General Rules
- Don't assume the
apiVersionof any Kubernetes or Flux resource — callget_kubernetes_api_versionsto find the correct one. - To determine if a Kubernetes resource is Flux-managed, look for
fluxcdlabels in the resource metadata. - After switching context to a new cluster, always call
get_flux_instanceto determine the Flux Operator status, version, and settings before doing anything else. - When creating or updating resources on the cluster, generate a Kubernetes YAML manifest
and call the
apply_kubernetes_manifesttool. When the target resource is managed by Flux, the tool errors unlessoverwriteis set totrue. Do not apply resources unless explicitly requested by the user. Before generating any YAML manifest, verify the exact field names and nesting against the field index inassets/schemas/. Index files follow the naming convention{kind}-{group}-{version}.fields.txt; each line is a dotted field path — grep by path prefix (e.g.grep '^spec\.' assets/schemas/kustomization-kustomize-v1.fields.txt) instead of reading the whole file (see the CRD reference table below). - You will not be able to read the values of Kubernetes Secrets, the MCP server will return only the
datafield with keys but empty values.
Cluster Context
If the user specifies a cluster name:
- Call
get_kubeconfig_contextsto list available contexts. - Find the context matching the user's cluster name.
- Call
set_kubeconfig_contextto switch to it. - Call
get_flux_instanceto verify the Flux installation on that cluster.
If no cluster is specified, debug on the current context. Still call get_flux_instance
at the start to understand the Flux installation.
What ships with it
22 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.3 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.0 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 8.3 KB
- evals/evals.json 3.2 KB
- references/flux-crds.md 14 KB
- references/troubleshooting.md 8.7 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.
- yesterday First seen · 257 lines · 96 tokens per session scan A 5164c8ffc62f
gitops-cluster-debug is a skill published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 96 tokens to every session and 3,910 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to gitops-cluster-debug, differing in 19 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…