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/AnthonyPoschen/agent-skillsnpx agentmods add skills/anthonyposchen/agent-skills/flux-kustomize-layoutWrote 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/anthonyposchen/agent-skills/flux-kustomize-layout)<a href="https://agentmods.dev/skills/anthonyposchen/agent-skills/flux-kustomize-layout"><img src="https://agentmods.dev/badge/skills/anthonyposchen/agent-skills/flux-kustomize-layout/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/anthonyposchen/agent-skills/flux-kustomize-layout"><img src="https://agentmods.dev/badge/skills/anthonyposchen/agent-skills/flux-kustomize-layout.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.00601 |
| Opus 5 | $0.00026 | $0.00300 |
| Sonnet 5 | $0.00011 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
flux-kustomize-layout 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 9d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flux Kustomize Layout
Goal
Create predictable FluxCD-friendly Kustomize layouts with one shared base and explicit dev/prod overlays. Keep the repository structure boring, discoverable, and easy for CI or Flux reconciliation to validate.
Required Layout
Always scaffold this structure unless the user explicitly asks otherwise:
kustomization/
base/
kustomization.yaml
overlays/
dev/
kustomization.yaml
prod/
kustomization.yaml
Rules
- Put shared Kubernetes manifests in
kustomization/base/. - Include every base manifest from
kustomization/base/kustomization.yaml. - Make
devandprodoverlays include../../base. - Put environment-specific patches, generators, images, labels, or namespace settings in the matching overlay folder.
- Keep base manifests environment-neutral unless the user asks for a different environment model.
- Prefer
apiVersion: kustomize.config.k8s.io/v1beta1andkind: Kustomizationfor Kustomize files. - Use lowercase file names with clear resource names, such as
deployment.yaml,service.yaml,configmap.yaml, andingress.yaml. - Do not put application manifests directly in overlay folders when they should be shared through base.
Minimal Files
Base kustomization.yaml:
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- deployment.yaml
- service.yaml
Overlay kustomization.yaml:
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- ../../base
Workflow
- Inspect existing Kubernetes, Kustomize, or Flux files before editing.
- Create missing directories and
kustomization.yamlfiles in the required layout. - Move shared manifests into
kustomization/base/when safe. - Add all shared manifests to the base resources list.
- Add
../../baseto each overlay resources list. - Put dev/prod differences in overlays as patches or Kustomize fields.
- If Flux
Kustomizationcustom resources are requested, keep them separate from Kustomizekustomization.yamlfiles and name the distinction clearly. - Validate with
kustomize buildorkubectl kustomizewhen available; otherwise report that validation was not run.
What ships with it
2 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.
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.
- 9d ago First seen · 82 lines · 53 tokens per session scan A 00326d49fef5
flux-kustomize-layout is a skill published in the GitHub repository AnthonyPoschen/agent-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 601 once invoked, about $0.0003 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-31.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.