Borrowing it
Nothing to install: this file belongs to openshift/external-secrets-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/external-secrets-operator/main/CLAUDE.mdgit clone --depth 1 https://github.com/openshift/external-secrets-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/external-secrets-operator/claude-md)<a href="https://agentmods.dev/instructions/openshift/external-secrets-operator/claude-md"><img src="https://agentmods.dev/badge/instructions/openshift/external-secrets-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/external-secrets-operator/claude-md"><img src="https://agentmods.dev/badge/instructions/openshift/external-secrets-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.00911 | $0.00911 |
| Opus 5.5 | $0.00364 | $0.00364 |
| Sonnet 5.5 | $0.00182 | $0.00182 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
external-secrets-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 yesterday.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@AGENTS.md
Build & Test Commands
Build
make build # Build operator with manifests, generate, fmt, vet
make build-operator # Build operator binary only (no checks)
make image-build # Build container image
Test
make test # Run all non-e2e tests (test-apis + test-unit)
make test-unit # Run unit tests only
make test-apis # Run API integration tests (envtest + Ginkgo)
make test-e2e # Run e2e tests (requires live cluster)
Lint & Verify
make lint # Run golangci-lint
make lint-fix # Run golangci-lint with auto-fix
make lint-markdown # Run markdownlint-cli2 on docs
make lint-markdown-fix # Auto-fix markdownlint findings where possible
make verify # Run vet, fmt, deps, bindata, generated files, govulncheck, markdownlint, git diff
make fmt # Run go fmt
make vet # Run go vet
Code Generation
make manifests # Generate CRDs and RBAC
make generate # Generate deepcopy methods
make update-bindata # Regenerate bindata.go from bindata/
make update # Run generate, manifests, update-operand-manifests, update-bindata, bundle, docs
Dependency Management
make update-vendor # Update vendor directory for all workspace modules
make update-dep PKG=... # Update a dependency across all modules
make verify-deps # Verify go.mod dependencies
Claude Code Behavioral Preferences
Commit Messages
Always include the Jira ticket number, a scope, and a clear imperative description. Format:
<JIRA-ID>: <scope>: short description of the change
Plain colons, no parens — OpenShift CI's jira-lifecycle-plugin maps PRs to Jira via a literal <TICKET>:/NO-JIRA: prefix, which a parenthesized scope would break.
Example: ESO-142: controller: add proxy egress network policy. A scope is always required. The Jira project can be any valid project (ESO, OAPE, etc.). If no Jira ticket exists, ask the user for context, or use NO-JIRA: <scope>: <imperative description> (e.g., NO-JIRA: docs: fix typo in README). Enforced by the commit-msg-jira-prefix pygrep hook in .pre-commit-config.yaml. Never use generic messages like "fix bug", "update code", or "address review comments".
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.
- yesterday First seen · 103 lines · 911 tokens per session scan A fa7cf558edf6
external-secrets-operator CLAUDE.md is an instructions file published in the GitHub repository openshift/external-secrets-operator (13 stars, last pushed 11d ago), licensed Apache-2.0. It adds 911 tokens to every session, about $0.0036 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-10-26.
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).
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).
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.