What is windows-machine-config-operator AGENTS.md?

Project instructions for the Windows Machine Config Operator, which configures Windows Server machines as worker nodes in OpenShift or OKD clusters. They describe the project, its components, and subscription and entitlement requirements.

Use them when working on the operator, Windows worker-node setup, certificate approval or rotation, environment management, or related OpenShift components.

They help a coding agent understand how Windows nodes, certificates, services, and cluster components fit together before making changes.

How openshift/windows-machine-config-operator configures Codex and Ope

Reuse

Borrowing it

Nothing to install: this file belongs to openshift/windows-machine-config-operator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/openshift/windows-machine-config-operator/master/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/openshift/windows-machine-config-operator

Made for: Codex, OpenCode.

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/instructions/openshift/windows-machine-config-operator/agents-md/github.svg)](https://agentmods.dev/instructions/openshift/windows-machine-config-operator/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/openshift/windows-machine-config-operator/agents-md"><img src="https://agentmods.dev/badge/instructions/openshift/windows-machine-config-operator/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/openshift/windows-machine-config-operator/agents-md"><img src="https://agentmods.dev/badge/instructions/openshift/windows-machine-config-operator/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 6,994 This file is loaded in full into every session.

When invoked 6,994 The same file — it is already loaded in full.

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

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.06994	$0.06994
Opus 5.5	$0.02798	$0.02798
Sonnet 5.5	$0.01399	$0.01399
Haiku 4.5	$0.00699	$0.00699

Measured 17d ago against content hash a0711796b5bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

windows-machine-config-operator 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 17d 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.

AGENTS.md · 781 lines

How it starts

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

AGENTS.md

Project Overview

The Windows Machine Config Operator (WMCO) configures Windows Server instances as worker nodes in OpenShift/OKD clusters, enabling Windows container workloads.

Architecture:

┌─────────────────────────────────────────────────────────────┐
│                    OpenShift Cluster                        │
├────────────────────────┬────────────────────────────────────┤
│   Linux Control Plane  │        Windows Worker Nodes        │
│  ┌──────────────────┐  │  ┌──────────────────────────────┐  │
│  │  WMCO Operator   │──┼──│  WICD (daemon)               │  │
│  │  - Controllers   │SSH│  │  - Service reconciliation    │  │
│  │  - CSR Approval  │  │  │  - Certificate rotation      │  │
│  └──────────────────┘  │  │  - Environment management    │  │
│                        │  └──────────────────────────────┘  │
│                        │  ┌──────────────────────────────┐  │
│                        │  │  Windows Components          │  │
│                        │  │  kubelet, containerd,        │  │
│                        │  │  kube-proxy, hybrid-overlay  │  │
│                        │  └──────────────────────────────┘  │
└────────────────────────┴────────────────────────────────────┘

Provisioning Modes:

Machine API: Create Windows VMs via MachineSets, auto-configured by WMCO
BYOH: Define existing instances in windows-instances ConfigMap

Tech Stack: Go (see go.mod for current version), Kubernetes Operator (controller-runtime), OpenShift APIs, Windows Server 2019/2022

Product Overview

Red Hat OpenShift support for Windows Containers is a layered component of OpenShift that allows the integration of Windows Nodes for running Windows Containers on an OpenShift 4 Cluster.

This is achieved by installing the Windows Machine Config Operator (WMCO), which runs on Linux based control-plane nodes. The WMCO bootstraps Windows nodes to join the cluster as Windows worker nodes.

Subscription Requirements

Read the full file on GitHub · 781 lines

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.

17d ago Changed · +70 lines · +1,828 tokens per session a0711796b5bc
18d ago Changed · +12 tokens per session e62fb368fd02
21d ago Changed · +3 lines · +27 tokens per session 1cafa1286ec0
2mo ago First seen · 708 lines · 5,127 tokens per session scan A caeeb30f4566

Subscribe to this mod's changes

windows-machine-config-operator AGENTS.md is an instructions file published in the GitHub repository openshift/windows-machine-config-operator (52 stars, last pushed yesterday), licensed Apache-2.0. It adds 6,994 tokens to every session, about $0.0280 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.

windows-machine-config-operator AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
windows-machine-config-operator AGENTS.mdopenshift/windows-machine-config-operator	Instructions file	52	yesterday	Apache-2.0	A	6,994	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

windows-machine-config-operator: Instructions file for Codex