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.
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.
curl -O https://raw.githubusercontent.com/Azure/gpt-rag-ingestion/main/.github/instructions/contracts-telemetry.instructions.mdgit clone --depth 1 https://github.com/Azure/gpt-rag-ingestionWrote 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/azure/gpt-rag-ingestion/contracts-telemetry)<a href="https://agentmods.dev/instructions/azure/gpt-rag-ingestion/contracts-telemetry"><img src="https://agentmods.dev/badge/instructions/azure/gpt-rag-ingestion/contracts-telemetry/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/azure/gpt-rag-ingestion/contracts-telemetry"><img src="https://agentmods.dev/badge/instructions/azure/gpt-rag-ingestion/contracts-telemetry.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.00249 | $0.00249 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
gpt-rag-ingestion contracts-telemetry.instructions.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 9d 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.
What it actually says
Shared audit contracts and telemetry
- Treat schema files and their SHA-256 pins as versioned cross-repository compatibility boundaries shared with Azure/GPT-RAG and the orchestrator.
- Keep logical schema, Application Insights wire schema, constants, golden fixtures, and integrity tests aligned with the exact committed bytes.
- Preserve the seven ingestion event types, run correlation, root-parent sentinel encoding, bounded payloads, and sanitization unless a coordinated contract change is approved.
- Never emit document text, raw source URLs, filenames, credentials, prompts, or other sensitive content in audit records.
- Provenance fields remain opt-in; strict governance defaults must not be represented as explicit document evidence.
- Audit creation, sanitization, or export failure remains logged and non-blocking. Do not apply best-effort behavior to source, indexing, deletion, or authorization failures.
- Add logical, wire, hash, sanitizer, correlation, and exporter-envelope tests for changed behavior.
- Do not claim legal or regulatory compliance from technical audit evidence.
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.
- 9d ago First seen · 24 lines · 249 tokens per session scan A 566e33869be2
gpt-rag-ingestion contracts-telemetry.instructions.md is an instructions file published in the GitHub repository Azure/gpt-rag-ingestion (189 stars, last pushed today), licensed MIT. It adds 249 tokens to every session, about $0.0012 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
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
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.
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.
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).
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).
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.