Borrowing it
Nothing to install: this file belongs to fluxcd/agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fluxcd/agent-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/fluxcd/agent-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/instructions/fluxcd/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/fluxcd/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/fluxcd/agent-skills/agents-md/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/instructions/fluxcd/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/fluxcd/agent-skills/agents-md.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.00809 | $0.00809 |
| Opus 5.5 | $0.00324 | $0.00324 |
| Sonnet 5.5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
agent-skills AGENTS.md 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 1mo 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This repository contains AI agent skills for Flux CD, Kubernetes, and GitOps. Skills follow the Agent Skills Open Standard.
Repository Layout
skills/{skill-name}/
├── SKILL.md # Agent instructions (frontmatter + workflow)
├── scripts/ # Helper scripts (thin bash wrappers around flux/flux-schema)
├── references/ # On-demand reference docs (checklists, API summaries)
├── assets/schemas/ # Bundled OpenAPI schemas for Flux CRDs
└── evals/evals.json # Evaluation scenarios with expected behavior
tests/{skill-name}/ # Test fixtures for offline evaluation
.claude-plugin/marketplace.json # Skill registry for distribution
Makefile # Schema downloads and test targets
skills/gitops-repo-audit/scripts/validate.shis vendored from the flux-schema action (the single source of truth). Don't edit it here — runmake sync-validateto refresh it, and send changes upstream.
Working on Existing Skills
- Read the skill's
SKILL.mdto understand its workflow and allowed tools - Read all files in
references/andscripts/before making changes - Keep
SKILL.mdunder ~15KB — heavy reference material belongs inreferences/
Running Skill Evals
Each skill has an evals/evals.json file with evaluation scenarios. When asked to run them:
- Read
evals/evals.jsonto get the list of eval prompts and their expectations - For each eval, spawn a sub-agent with this prompt template:
You are a [skill role]. load the skill from `skills/{skill-name}/SKILL.md` exactly — read it first, then follow the workflow phases. Your task: [eval prompt from evals.json] Important: - Do not seach the web, use only the skill references and your own reasoning - Produce the full structured report as specified in the workflow if there is one - Score each eval output against the
expectationsarray — each expectation is a pass/fail check - Report results as a scorecard: eval id, pass/fail counts, and any missed expectations
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.
- 1mo ago First seen · 69 lines · 809 tokens per session scan A bcb3f5d7ea99
agent-skills AGENTS.md is an instructions file published in the GitHub repository fluxcd/agent-skills (233 stars, last pushed 7d ago), licensed Apache-2.0. It adds 809 tokens to every session, about $0.0032 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.