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.
curl -O https://raw.githubusercontent.com/openshift/service-ca-operator/main/CLAUDE.mdgit clone --depth 1 https://github.com/openshift/service-ca-operatorWrote 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/openshift/service-ca-operator/claude-md)<a href="https://agentmods.dev/instructions/openshift/service-ca-operator/claude-md"><img src="https://agentmods.dev/badge/instructions/openshift/service-ca-operator/claude-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/openshift/service-ca-operator/claude-md"><img src="https://agentmods.dev/badge/instructions/openshift/service-ca-operator/claude-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.01546 | $0.01546 |
| Opus 5.5 | $0.00618 | $0.00618 |
| Sonnet 5.5 | $0.00309 | $0.00309 |
| Haiku 4.5 | $0.00155 | $0.00155 |
Grade A, and why
service-ca-operator CLAUDE.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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service CA Operator — AI Assistant Guidelines
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build & Test Commands
# Build everything (operator binary + OTE test binary)
make build
# Run unit tests
make test-unit
# Run a single unit test
go test ./pkg/operator/ -run TestSyncName -count 1
# Run e2e tests (requires cluster access)
make test-e2e
# Verify all generated files
make verify
# Update all generated files
make update
# Update vendored dependencies
go mod tidy && go mod vendor
Architecture
This is an OpenShift ClusterOperator with a two-process architecture running from a single binary (service-ca-operator):
Operator Process (service-ca-operator operator)
- Package:
pkg/operator/ - Has two main responsibilities:
- Operand lifecycle: Manages the controller Deployment in the
openshift-service-canamespace, syncing static resources (namespace, service account, RBAC, deployment) from embedded assets - Signing CA management: Creates and rotates the signing CA keypair (Secret) and maintains the CA bundle ConfigMap
- Operand lifecycle: Manages the controller Deployment in the
- Reports the "service-ca" ClusterOperator status conditions
Controller Process (service-ca-operator controller)
- Package:
pkg/controller/ - Started by the operator as a Deployment; runs three controllers:
- Serving Cert Signer (
pkg/controller/servingcert/): Signs TLS serving certs for Services annotated withservice.beta.openshift.io/serving-cert-secret-name - ConfigMap CA Bundle Injector (
pkg/controller/cabundleinjector/configmap.go): Injects the CA bundle into ConfigMaps annotated withservice.beta.openshift.io/inject-cabundle=true - Generic CA Bundle Injector (
pkg/controller/cabundleinjector/): Injects the CA bundle into APIServices, MutatingWebhookConfigurations, ValidatingWebhookConfigurations, and CRDs with the same annotation
- Serving Cert Signer (
Embedded Assets
Static resource manifests are embedded using Go's native embed.FS:
- Asset location:
bindata/assets/*.yaml - Embed declaration:
bindata/assets.go(uses//go:embed assets/*.yaml) - Usage:
bindata.MustAsset("assets/<filename>.yaml")to read asset bytes at runtime - No code generation step is required — assets are embedded at compile time
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 · 102 lines · 1,546 tokens per session scan A 3da2d8cb2178
service-ca-operator CLAUDE.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,546 tokens to every session, about $0.0062 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
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
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).