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/service-ca-operator/agents-mdgit clone --depth 1 https://github.com/openshift/service-ca-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.01077 | $0.01077 |
| Opus 5 | $0.00539 | $0.00539 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00108 | $0.00108 |
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 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 — 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
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 · 76 lines · 1,077 tokens per session scan A 59acda0a1018
service-ca-operator AGENTS.md is an instructions file published in the GitHub repository openshift/service-ca-operator (47 stars, last pushed 16d ago), licensed Apache-2.0. It adds 1,077 tokens to every session, about $0.0054 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
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.