What is gitops-repo-audit?

A checker for Flux CD GitOps repositories. GitOps is a way to manage deployments through files in a repository, while Flux CD applies those files to Kubernetes.

Use it to inspect repository files, validate Kubernetes resources, review Flux APIs, check permissions and secrets handling, and produce a prioritized report.

It finds invalid Kubernetes files, outdated Flux settings, and security or access-control problems before they affect a live cluster.

gitops-repo-audit — Skill for Claude Code by fluxcd/agent-skills

Install

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.

Any agent

npx skills add fluxcd/agent-skills --skill gitops-repo-audit

Clone the repo

git clone --depth 1 https://github.com/fluxcd/agent-skills

Made for: Claude Code.

Or install gitops-skills, the plugin that ships this one along with the rest of its 3 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/fluxcd/agent-skills/gitops-repo-audit/github.svg)](https://agentmods.dev/skills/fluxcd/agent-skills/gitops-repo-audit)

Your own site

<a href="https://agentmods.dev/skills/fluxcd/agent-skills/gitops-repo-audit"><img src="https://agentmods.dev/badge/skills/fluxcd/agent-skills/gitops-repo-audit/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/fluxcd/agent-skills/gitops-repo-audit"><img src="https://agentmods.dev/badge/skills/fluxcd/agent-skills/gitops-repo-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,577 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 25 Oct 2026
Snyk pass 25 Oct 2026
NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00076	$0.03577
Opus 5.5	$0.00030	$0.01431
Sonnet 5.5	$0.00015	$0.00715
Haiku 4.5	$0.00008	$0.00358

Measured today against content hash 22aabcde2ba1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gitops-repo-audit 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 today.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/check-deprecated.sh, scripts/discover.sh, scripts/validate.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/gitops-repo-audit/SKILL.md · 196 lines

How it starts

The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitOps Repository Auditor

You are a GitOps repository auditor specialized in Flux CD. Your job is to examine GitOps repositories, identify issues, validate manifests, audit security posture, and provide actionable recommendations for improvement.

When auditing a repository, follow the workflow below. Adapt the depth based on what the user asks for — a targeted question ("are my HelmReleases configured correctly?") doesn't need the full workflow; a broad request ("audit this repo") does.

Analysis Workflow

Phase 1: Discovery

Understand the repository before diving into specifics.

Run the bundled discovery script to get a Kubernetes resource inventory:
```
scripts/discover.sh -d <repo-root>
```
The script wraps flux-schema discover and outputs JSON with a top-level inventory object (alongside kind/apiVersion/$schema) containing: a summary (file, resource, and line counts), a directories map classifying each directory as kubernetes-manifests, kustomize-overlay, helm-chart, or terraform, a resources map with counts keyed by group/version/Kind, and a flux map listing every Flux resource per file. Read the fields under .inventory. Multi-document files are handled.
Classify the repository pattern by reading repo-patterns.md and matching against the heuristics table
Detect clusters: look for directories under clusters/ or FluxInstance resources. Read the FluxInstance to understand how the clusters are configured.
Check for gotk-sync.yaml under flux-system/ — its presence indicates flux bootstrap was used. Recommend migrating to the Flux Operator with a FluxInstance resource. Always include the migration guide URL in the report: https://fluxoperator.dev/docs/guides/migration/

Phase 2: Manifest Validation

Run the bundled validation script to check Kubernetes schemas and Kustomize builds. Write the rendered bundle to a temp file (never in the repo) so Phases 4–5 can grep the effective manifests. Use mktemp so the path is unique — concurrent audits on the same machine must not overwrite each other's bundles. If tmp is not writable, mktemp fails and the script runs without the bundle:

Read the full file on GitHub · 196 lines

Files

What ships with it

31 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.

Changes

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.

today Changed · -2 lines 22aabcde2ba1
yesterday Changed · +4 lines 605e9bdc9adb
1mo ago First seen · 194 lines · 76 tokens per session scan A 54f7177812a8

Subscribe to this mod's changes

gitops-repo-audit is a skill published in the GitHub repository fluxcd/agent-skills (236 stars, last pushed yesterday), licensed Apache-2.0. It adds 76 tokens to every session and 3,577 once invoked, about $0.0003 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.

Cloud DevOps and cloud Security agent-skills ai-agents fluxcd gitops skills

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).

google/skills · 64 tokens

application-integration-authoring

Builds, versions, publishes, tests, and executes Google Cloud Application Integration workflows through the REST API and Python discovery client, and promotes versions across environments. Use when listing integrations, downloading or uploading integration versions as JSON, configuring API triggers or config…

google/skills · 103 tokens

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…

google/skills · 83 tokens

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…

google/skills · 120 tokens

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…

google/skills · 108 tokens

application-integration-basics

Explains Google Cloud Application Integration concepts, region provisioning, IAM roles, run-as service accounts, interface choices (REST, Python discovery client, Terraform, ADK), and platform limits. Use when setting up Application Integration in a Google Cloud project, enabling required APIs, provisioning a region…

google/skills · 122 tokens