gpt-rag-ingestion: Instructions file for Codex

AGENTS.md

gpt-rag-ingestion AGENTS.md is an instructions file for Codex, OpenCode from Azure/gpt-rag-ingestion. It costs 1,304 tokens per session, scanned A, original, MIT.

Repository-wide instructions for Azure's GPT-RAG ingestion project, which converts source documents into searchable chunks and embeddings for Azure AI Search. They define the agent's responsibilities, priorities, security boundaries, and the project's main systems.

In plain words
What is it for?
Use them when working on document ingestion, search indexing, authorization, configuration, security-sensitive changes, or the project's APIs and dashboards.
Why use it?
They help an agent avoid guessing about sensitive indexed data, permissions, shared contracts, and production jobs.

Instructions file for CodexOpenCode ✓ vendor

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

This is Azure/gpt-rag-ingestion's own configuration. It tells Codex and OpenCode how to work on gpt-rag-ingestion 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 gpt-rag-ingestion configures →

About the project

GPT-RAG Data Ingestion is a service that processes documents such as PDFs, images, spreadsheets, transcripts, and SharePoint files so they can be searched through Azure AI Search. It prepares data with format-specific chunking and text or image embeddings for multimodal retrieval in agent-based applications.

Azure/gpt-rag-ingestion · 189 stars · on GitHub

Reuse

Borrowing it

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

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 gpt-rag-ingestion AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/azure/gpt-rag-ingestion/agents-md.svg)](https://agentmods.dev/instructions/azure/gpt-rag-ingestion/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/azure/gpt-rag-ingestion/agents-md"><img src="https://agentmods.dev/badge/instructions/azure/gpt-rag-ingestion/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,304 This file is loaded in full into every session.
When invoked 1,304 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.01304 $0.01304
Opus 5 $0.00652 $0.00652
Sonnet 5 $0.00261 $0.00261
Haiku 4.5 $0.00130 $0.00130

Measured 8d ago against content hash c5c2114ddbe7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

gpt-rag-ingestion 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 8d 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 · 135 lines

How it starts

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

GPT-RAG ingestion engineering-agent contract

This is the stable repository-wide contract for GitHub Copilot engineering agents. Detailed procedures belong in .github/skills/; path-specific rules belong in .github/instructions/; branching and release policy remains in .github/copilot-instructions.md.

Priority

Follow, in order:

  1. Security, privacy, authorization, and platform instructions.
  2. Task requirements and acceptance criteria.
  3. Executable configuration and versioned contracts in this repository.
  4. .github/copilot-instructions.md, this contract, and applicable scoped instructions.
  5. Local conventions in the affected code.

Do not guess behavior that could affect indexed data, document authorization, shared contracts, production jobs, or releases. Record uncertainty and obtain a human decision.

What this repository is

gpt-rag-ingestion is the Python 3.12 data plane that turns source documents into chunks and embeddings and writes them to Azure AI Search. It supports Blob Storage, SharePoint, NL2SQL, multimodal content, scheduled ingestion and purge jobs, versioned audit events, a FastAPI operator API, and a React operator dashboard.

The repository is one runtime component of Azure/GPT-RAG. Shared deployment, configuration, contracts, and release pins must remain compatible with the umbrella repository and other consumers.

The files under .github/agents/ define Copilot engineering roles used to develop and operate this repository. They are not runtime ingestion agents. The modules under jobs/ and the APScheduler registrations in main.py are runtime workers executed by the ingestion service; never describe or modify them as Copilot agents.

Repository boundaries

  • chunking/: document orchestration and format-specific chunkers selected through chunking/chunker_factory.py.
  • jobs/: long-running index, purge, and source synchronization workers.
  • tools/: Azure and source-system adapters, credentials, and clients.
  • api/: thin FastAPI operator endpoints.
  • frontend/: React/Vite operator dashboard.
  • telemetry/: OpenTelemetry and versioned ingestion audit behavior.
  • contracts/: shared schema bytes and integrity pins.
  • scripts/, azure.yaml, Dockerfile, and infra/: build, deployment, and Azure runtime surfaces.
  • tests/: focused Python behavior and contract tests.

Read the full file on GitHub · 135 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. 8d ago First seen · 135 lines · 1,304 tokens per session scan A c5c2114ddbe7

Subscribe to this mod's changes

gpt-rag-ingestion AGENTS.md is an instructions file published in the GitHub repository Azure/gpt-rag-ingestion (189 stars, last pushed yesterday), licensed MIT. It adds 1,304 tokens to every session, about $0.0065 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.

Related

Other instructions, from other repositories

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,296 tokens

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.

openai/codex · 5,153 tokens

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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

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.

github/spec-kit · 7,104 tokens