service-ca-operator: Instructions file for Codex

AGENTS.md

service-ca-operator AGENTS.md is an instructions file for Codex, OpenCode from openshift/service-ca-operator. It costs 1,077 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for OpenShift's service-ca-operator. OpenShift is Red Hat's Kubernetes platform, and this operator manages a certificate authority that creates TLS certificates for services inside a cluster.

In plain words
What is it for?
Use them when developing, testing, reviewing, or navigating the service-ca-operator, including its certificate-signing controller and cluster resources.
Why use it?
They explain the repository structure, architecture, required reference documents, and rules an agent must follow when changing the code.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is openshift/service-ca-operator's own configuration. It tells Codex and OpenCode how to work on service-ca-operator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything service-ca-operator configures →

Reuse

Borrowing it

Nothing to install: this file belongs to openshift/service-ca-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/service-ca-operator/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/openshift/service-ca-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.

agentmods badge for service-ca-operator AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/openshift/service-ca-operator/agents-md/github.svg)](https://agentmods.dev/instructions/openshift/service-ca-operator/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/openshift/service-ca-operator/agents-md"><img src="https://agentmods.dev/badge/instructions/openshift/service-ca-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.

agentmods 80×15 button for service-ca-operator AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/openshift/service-ca-operator/agents-md"><img src="https://agentmods.dev/badge/instructions/openshift/service-ca-operator/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,077 This file is loaded in full into every session.
When invoked 1,077 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01077 $0.01077
Opus 5.5 $0.00431 $0.00431
Sonnet 5.5 $0.00215 $0.00215
Haiku 4.5 $0.00108 $0.00108

Measured 1mo ago against content hash 59acda0a1018, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

service-ca-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 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.

AGENTS.md · 76 lines

How it starts

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

AI Agent Instructions for service-ca-operator

Also read ARCHITECTURE.md for design decisions, CONTRIBUTING.md for PR workflow, OWNERS for reviewers/approvers.

What This Repo Is

An OpenShift ClusterOperator that manages the service-serving CA — a cluster-scoped certificate authority that automatically provisions TLS certificates for in-cluster Services. The operator manages the CA keypair and deploys a controller that signs serving certificates and injects CA bundles into annotated resources.

Two-process architecture from a single binary (service-ca-operator):

  • Operator (pkg/operator/): Manages the signing CA, controller Deployment lifecycle, and ClusterOperator status
  • Controller (pkg/controller/): Signs TLS certs for annotated Services, injects CA bundles into ConfigMaps/APIServices/Webhooks/CRDs

Repository Layout

cmd/service-ca-operator/           Single binary, two subcommands: operator | controller
cmd/service-ca-operator-tests-ext/ OTE e2e test binary
pkg/operator/                      Operator process — CA lifecycle, deployment sync, status
pkg/controller/                    Controller process — serving cert signer, CA bundle injectors
pkg/controller/api/                Annotation constants, resource names
pkg/controller/cabundleinjector/   CA bundle injection into ConfigMaps, webhooks, CRDs, APIServices
pkg/controller/servingcert/        Serving cert signing controller
pkg/cmd/                           CLI wiring (cobra commands)
bindata/assets/                    Embedded static manifests (Go embed.FS)
manifests/                         CVO-managed manifests (operator deployment, RBAC, monitoring)
profile-patches/                   HyperShift / managed profile patches
test/e2e/                          E2e tests (OTE framework)

Build and Test Commands

make build                                           # Build operator + OTE test binary
make test-unit                                        # Run all unit tests
go test ./pkg/operator/ -run TestName -count 1        # Single unit test
make test-e2e                                         # E2e tests (requires cluster + KUBECONFIG)
make verify                                           # Verify generated files
make update                                           # Update generated files
go mod tidy && go mod vendor                          # Update vendored dependencies

Read the full file on GitHub · 76 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.

  1. 1mo ago First seen · 76 lines · 1,077 tokens per session scan A 59acda0a1018

Subscribe to this mod's changes

service-ca-operator AGENTS.md is an instructions file published in the GitHub repository openshift/service-ca-operator (47 stars, last pushed 10d ago), licensed Apache-2.0. It adds 1,077 tokens to every session, about $0.0043 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens