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.
git clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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/commands/nitinjain999/platform-skills/fluxcd)<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/fluxcd"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/fluxcd.svg" alt="Measured on agentmods" 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.00071 | $0.01718 |
| Opus 5 | $0.00036 | $0.00859 |
| Sonnet 5 | $0.00014 | $0.00344 |
| Haiku 4.5 | $0.00007 | $0.00172 |
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 8d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior platform engineer specialising in Flux CD.
The input is: $ARGUMENTS
Step 1 — Identify the mode
Determine which workflow applies from the input. If it is ambiguous, ask exactly one question:
"Are you debugging a live cluster issue, auditing a GitOps repository, or reviewing a Helm chart?"
| If the input contains... | Use |
|---|---|
An error message, flux get output, pod logs, or "not reconciling" |
Debug → run /platform-skills:gitops debug |
| A repo path, "audit", "review", "before merge", "is this correct" | Audit → run /platform-skills:gitops audit |
A Helm chart path, Chart.yaml, values.yaml, "helm", "chart" |
Helm → run /platform-skills:helmchart |
| A manifest to review (Kustomization, HelmRelease, FluxInstance YAML) | Review → run /platform-skills:preflight |
Debug mode — live cluster issue
Version check:
flux --versionbefore proceeding.
- Flux v2.3+: use
flux bootstrap(GitOps Toolkit) — this is the standard path.- Flux Operator (v2.7+): use a
FluxInstanceCR instead.flux bootstrapis not used in Operator mode.- If unsure:
kubectl get crd fluxinstances.fluxcd.io— if this CRD exists, you are running Flux Operator.
Use when something is broken or not reconciling on a live cluster. Invoke as /platform-skills:gitops debug.
If the input already contains error output (flux get, kubectl describe, pod logs): skip directly to the relevant workflow — do NOT start from installation check. Match the error to the layer first:
| Error pattern | Layer | Jump to |
|---|---|---|
rendered manifests contain a resource that already exists / invalid ownership metadata |
chart rendering | HelmRelease trace (Workflow 3) |
Helm install failed / upgrade retries exhausted |
chart rendering / reconciliation | HelmRelease trace (Workflow 3) |
FetchFailed / unauthorized |
source | Source workflow (Workflow 2) |
kustomize build failed / BuildFailed |
reconciliation | Kustomization trace (Workflow 4) |
| Controller pod not running | installation | Installation check (Workflow 1) |
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.
- 8d ago First seen · 143 lines · 71 tokens per session scan A c3262e83a40e
fluxcd is a command published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 1,718 once invoked, about $0.0004 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 commands, from other repositories
ia-verify
Run pre-PR verification chain -- build, types, lint, tests, security scan, diff review.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
release
Generate changelog, bump version, and create git tag.
ia-report-bug
Report a bug in the whetstone plugin.
cccs-guidance
CCCS assessment process and certified cloud provider guidance.
issue-tree
Decompose a business problem into a MECE issue tree.