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/kubernetes-sigs/cluster-api-provider-openstack/agents-mdgit clone --depth 1 https://github.com/kubernetes-sigs/cluster-api-provider-openstackWrote 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/kubernetes-sigs/cluster-api-provider-openstack/agents-md)<a href="https://agentmods.dev/instructions/kubernetes-sigs/cluster-api-provider-openstack/agents-md"><img src="https://agentmods.dev/badge/instructions/kubernetes-sigs/cluster-api-provider-openstack/agents-md.svg" alt="Measured on agentmods" 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 | $0.02018 | $0.02018 |
| Opus 5 | $0.01009 | $0.01009 |
| Sonnet 5 | $0.00404 | $0.00404 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
cluster-api-provider-openstack 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Agent Guidelines for Cluster API Provider OpenStack
This document provides guidelines and useful commands for AI agents contributing to the Cluster API Provider OpenStack (CAPO) repository.
⚠️ IMPORTANT: When making changes to Makefile targets, PR requirements, code generation workflows, verification steps, or any other information referenced in this document, AGENTS.md must be updated accordingly to keep it synchronized with the actual project state.
Overview
Cluster API Provider OpenStack (CAPO) is a Kubernetes-native declarative infrastructure provider for managing Kubernetes clusters on OpenStack. It implements the Cluster API (CAPI) specification for self-managed Kubernetes clusters on OpenStack infrastructure.
Key Concepts:
- CAPI: Cluster API - the upstream Kubernetes project defining cluster lifecycle APIs
- CAPO: Cluster API Provider OpenStack - this repository
- Reconciler: Controller-runtime pattern for managing Kubernetes custom resources
- Scope: Context and configuration wrapper for controllers and services
Key Requirements for Contributors
Legal Requirements
- CLA Required: All contributors MUST sign the Kubernetes Contributor License Agreement (CLA)
- See: https://git.k8s.io/community/CLA.md
Pull Request Labels
All code PRs MUST be labeled with one of:
- ⚠️
:warning:- major or breaking changes - ✨
:sparkles:- feature additions - 🐛
:bug:- patch and bugfixes - 📖
:book:- documentation or proposals - 🌱
:seedling:- minor or other
Essential Make Targets
Code Quality & Verification
⚠️ IMPORTANT: The
make verifytargets compare the working tree againstHEAD(the last commit). This means:
make verifywill always fail if you have uncommitted changes, even if those changes are correct- You should commit your changes first, then run
make verifyto confirm everything is in order- The typical workflow is: make changes →
make generate→make modules→make test→ commit →make verify
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 · 304 lines · 2,018 tokens per session scan A 3654aff7322e
cluster-api-provider-openstack AGENTS.md is an instructions file published in the GitHub repository kubernetes-sigs/cluster-api-provider-openstack (367 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,018 tokens to every session, about $0.0101 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-09-01.
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).
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.
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.
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 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).
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.