security: Instructions file for Codex

AGENTS.md

security AGENTS.md is an instructions file for Codex, OpenCode from opensearch-project/security. It costs 2,250 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for AI coding agents working on OpenSearch Security, a plugin that adds authentication, permissions, encryption, audit logging, and multi-tenancy to OpenSearch.

In plain words
What is it for?
Use them when changing or reviewing this project so build requirements, security constraints, contribution practices, and AGENTS.md maintenance are followed.
Why use it?
They explain the repository's structure and rules, including when documentation must be updated alongside code changes.

Instructions file for CodexOpenCode

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

This is opensearch-project/security's own configuration. It tells Codex and OpenCode how to work on security 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 security configures →

Reuse

Borrowing it

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

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 security AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/opensearch-project/security/agents-md"><img src="https://agentmods.dev/badge/instructions/opensearch-project/security/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,250 This file is loaded in full into every session.
When invoked 2,250 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.02250 $0.02250
Opus 5.5 $0.00900 $0.00900
Sonnet 5.5 $0.00450 $0.00450
Haiku 4.5 $0.00225 $0.00225

Measured 10d ago against content hash 9eea075215e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security 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 10d 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 · 226 lines

How it starts

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

AGENTS.md — OpenSearch Security Plugin

Guidance for AI coding agents working in this repository.

Keeping This File Up to Date

This file should be updated automatically as part of any change that affects the information documented here. Do not treat it as a separate maintenance task — include the AGENTS.md update in the same commit or PR as the relevant code change. Examples of changes that should trigger an update:

  • Adding, removing, or renaming source packages or top-level directories
  • Changing the build system, required JDK version, or key Gradle tasks
  • Adding or retiring test suites or testing conventions
  • Changing code style tooling or static analysis configuration
  • Updating contribution workflows (branching strategy, backport process, commit conventions, etc.)
  • Adding new security-specific patterns or constraints agents should be aware of

When in doubt, update the file.

Repository Overview

OpenSearch Security is a plugin that adds authentication, authorization, TLS encryption, audit logging, and multi-tenancy to OpenSearch. The plugin intercepts all requests at the REST and transport layers before they reach OpenSearch action handlers.

See docs/ARCHITECTURE.md for detailed flow diagrams.

Repository Structure

src/
  main/java/org/opensearch/security/
    action/         # Custom OpenSearch actions registered by the plugin
    auditlog/       # Audit and compliance logging framework
    auth/           # Authentication backends (basic, PKI, proxy, LDAP, Kerberos, JWT, OIDC, SAML)
    authtoken/      # On-behalf-of (OBO) token issuance for extensions
    compliance/     # Field-level security and compliance (GDPR/HIPAA/PCI/SOX) features
    configuration/  # Security index management, config hot-reload
    dlic/           # Dynamic configuration REST API (roles, users, role-mappings, etc.)
    filter/         # REST and transport request/response filter pipeline
    hasher/         # Password hashing utilities
    http/           # HTTP/HTTPS layer integration
    httpclient/     # Internal HTTP client for auth backend calls
    identity/       # Subject and identity abstractions
    opensaml/       # OpenSAML integration utilities
    privileges/     # Authorization engine (role evaluation, DLS/FLS)
    queries/        # DLS query building
    resources/      # Resource sharing and access control
    rest/           # REST action handlers and route registration
    securityconf/   # Security configuration model (roles, mappings, users)
    setting/        # Plugin settings definitions
    ssl/            # TLS configuration for transport and HTTP layers
    state/          # Cluster security state management
    support/        # Shared support utilities
    tools/          # Admin tools (securityadmin)
    transport/      # Transport layer interception and enforcement
    user/           # User model and attribute handling
    util/           # General utilities
  test/             # Unit tests
  integrationTest/  # Integration tests (require a running OpenSearch cluster)
spi/                # Security Plugin Interface — public extension points for other plugins
libs/
  opensaml/         # Vendored/shaded OpenSAML library
sample-resource-plugin/  # Example plugin using the resource-sharing SPI
config/             # Default demo configuration (certs, roles, users, mappings)
docs/               # Contributor guides (developer guide, architecture, triaging, resource sharing)
tools/              # Shell scripts: securityadmin.sh, install_demo_configuration.sh
scripts/            # CI/CD helper scripts
bwc-test/           # Backwards-compatibility tests
checkstyle/         # Checkstyle rule configuration
formatter/          # Eclipse JDT formatter configuration

Read the full file on GitHub · 226 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. 10d ago Changed · +1 lines · +26 tokens per session 9eea075215e7
  2. 19d ago Changed · +1 lines · +26 tokens per session 7f429e50f2fa
  3. 1mo ago Changed · +3 lines · +51 tokens per session 2458c4f610e1
  4. 1mo ago First seen · 221 lines · 2,147 tokens per session scan A 7b0449e04df5

Subscribe to this mod's changes

security AGENTS.md is an instructions file published in the GitHub repository opensearch-project/security (255 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,250 tokens to every session, about $0.0090 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