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.
npx agentmods add instructions/openshift/windows-machine-config-operator/agents-mdgit clone --depth 1 https://github.com/openshift/windows-machine-config-operatorWhat 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 | $0.05127 | $0.05127 |
| Opus 5 | $0.02563 | $0.02563 |
| Sonnet 5 | $0.01025 | $0.01025 |
| Haiku 4.5 | $0.00513 | $0.00513 |
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 2d 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 — 708 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-instancesConfigMap
Tech Stack: Go 1.24+, 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
Windows Containers requires a specific subscription, in addition to an OpenShift Container Platform subscription:
- Worker nodes only - Control plane and infrastructure nodes don't need a paid subscription for Windows Containers
- When working cases, verify entitlement mapping to ensure compliance
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.
- 2d ago First seen · 708 lines · 5,127 tokens per session scan A caeeb30f4566
windows-machine-config-operator AGENTS.md is an instructions file published in the GitHub repository openshift/windows-machine-config-operator (51 stars, last pushed 3d ago), licensed Apache-2.0. It adds 5,127 tokens to every session, about $0.0256 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.