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/instana/instana-agent-operator/agents-mdgit clone --depth 1 https://github.com/instana/instana-agent-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/instana/instana-agent-operator/agents-md)<a href="https://agentmods.dev/instructions/instana/instana-agent-operator/agents-md"><img src="https://agentmods.dev/badge/instructions/instana/instana-agent-operator/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.01381 | $0.01381 |
| Opus 5 | $0.00691 | $0.00691 |
| Sonnet 5 | $0.00276 | $0.00276 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
instana-agent-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 4d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to agents when working with code in this repository.
Build & Test Commands
- Build:
make build - Lint:
make lint - Format:
make fmtor format specific file:./bin/golangci-lint fmt ./path/to/file - Run tests:
make test(excludes mocks and e2e directories) - Run single test:
go test -v ./path/to/package -run TestName - E2E tests:
make e2e(requirese2e/.envfile - copy frome2e/.env.example) - Install golangci-lint if missing:
make golangci-lint - Validate renovate.json:
npx --yes --package renovate -- renovate-config-validator - Secrets baseline:
detect-secrets scan --update .secrets.baselinebefore committing - Secrets audit:
detect-secrets audit .secrets.baseline
Code Style
- Go version: Check
go.modtoolchain directive (currently go 1.25.0) - Line length: 120 characters max (enforced by lll linter)
- Linters: See
.golangci.ymlfor full configuration (govet, ineffassign, unused, misspell, exhaustive, errcheck, lll) - Commit messages: MUST include DCO sign-off with
git commit -s. Use conventional commits syntax for subject, concise message with brief summary in body
Project-Specific Rules (Non-Obvious Only)
- Error wrapping: MUST use
github.com/pkg/errorspackage (not standard library errors) - Tools directory: All binaries install to
./bin/(GOBIN override in Makefile) - Branch naming: Avoid
/in branch names (breaks SPS/Tekton CI pipeline task names) - Container builds: Uses buildctl with containerized buildkitd (not direct docker build)
- PR template: Fill out
.github/pull_request_template.mdand use as PR body
Kubernetes Operator Specifics
- Finalizers: Two versions exist (finalizerV1 and finalizerV3) in controllers, prefer finalizerV3
- ETCD discovery: Automatic on OpenShift - copies certs from openshift-etcd namespace to instana-agent
- Namespace handling: Default namespace is
instana-agent, notdefault - CRD versions: InstanaAgent has both v1 and v1beta1, RemoteAgent only v1
- OpenShift detection: Uses
occommand availability to detect OCP vs vanilla K8s - Local dev:
make dev-run-clusterfor full setup,make runto run operator locally - Cleanup:
make purgeremoves all cluster resources including finalizers
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.
- 4d ago First seen · 97 lines · 1,381 tokens per session scan A 278b5617f030
instana-agent-operator AGENTS.md is an instructions file published in the GitHub repository instana/instana-agent-operator (49 stars, last pushed today), licensed Apache-2.0. It adds 1,381 tokens to every session, about $0.0069 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.