agentmods.dev

GPT-RAG: Instructions file for GitHub Copilot

.github/copilot-instructions.md

GPT-RAG copilot-instructions.md is an instructions file for GitHub Copilot from Azure/GPT-RAG. It costs 1,899 tokens per session, scanned A, original, MIT.

Repository development and release instructions for an Azure/GPT-RAG project. They define how work moves between development, feature, release, and stable branches.

In plain words
What is it for?
Use them to create branches, prepare feature pull requests, and follow the repository's release workflow.
Why use it?
They reduce mistakes such as starting from the wrong branch or sending feature work directly to the stable release branch. They also make the expected development and release process clear.

Instructions file for GitHub Copilot ✓ vendor

Written for GitHub Copilot: a Copilot instructions file.

This is Azure/GPT-RAG's own configuration. It tells GitHub Copilot how to work on GPT-RAG 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 configures →

not rated 1.2krepo 1mo ago A scan 1,899 tokens original MIT
View source ↗ Azure/GPT-RAG aka.ms
About the project

GPT-RAG is an Azure solution accelerator for building agentic retrieval-augmented generation systems, where agents use connected organizational sources to ground their answers. It is for organizations deploying secure RAG applications with Microsoft Foundry, Microsoft Agent Framework, and Azure infrastructure. The catalogue add-ons provide agents, skills, and instructions for deploying and working with the accelerator.

Azure/GPT-RAG · 1,179 stars · on GitHub · aka.ms

Reuse

Borrowing it

Nothing to install: this file belongs to Azure/GPT-RAG. 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/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/Azure/GPT-RAG

Made for: GitHub Copilot.

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 copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/azure/gpt-rag/copilot-instructions/github.svg)](https://agentmods.dev/instructions/azure/gpt-rag/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/azure/gpt-rag/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/azure/gpt-rag/copilot-instructions/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 GPT-RAG copilot-instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/azure/gpt-rag/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/azure/gpt-rag/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,899 This file is loaded in full into every session.
When invoked 1,899 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.01899 $0.01899
Opus 5.5 $0.00760 $0.00760
Sonnet 5.5 $0.00380 $0.00380
Haiku 4.5 $0.00190 $0.00190

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

Security

Grade A, and why

GPT-RAG copilot-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 2mo 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.

.github/copilot-instructions.md · 241 lines

How it starts

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

Repository Development and Release Instructions

Overview

This repository follows a structured workflow based on two primary branches:

  • develop → ongoing development
  • main → stable, released versions

All work must follow the branching, versioning, and changelog rules defined below.

Branching Strategy

Default Behavior

Unless explicitly instructed otherwise:

  • All development work MUST start from develop
  • All new work MUST be done in a feature branch
  • Feature work MUST target develop
  • Release preparation MUST target main

Feature Development Workflow

Branch Creation

  • Always create feature branches from develop
  • Naming convention:
    • feature/<short-description>

Examples:

  • feature/conversation-metadata
  • feature/improve-chat-history

Feature Pull Requests

  • Source branch: feature/*
  • Target branch: develop
  • Never target main from a feature branch

Expected Flow

  1. Start from develop
  2. Create feature/<name>
  3. Implement changes
  4. Commit changes
  5. Open pull request to develop

Release Workflow

Release Branch Creation

  • Release branches MUST be created from develop
  • Naming convention:
    • release/x.y.z (no v prefix)

Examples:

  • release/1.2.3
  • release/2.4.2

Release Responsibilities

When preparing a release branch:

  • Update version references where applicable
  • Update CHANGELOG.md
  • Ensure the repository reflects a releasable state
  • Do NOT introduce new feature work
  • GitHub Release titles MUST be exactly the tag name (for example, v2.8.0). Never prefix release titles with the product or service name (for example, do not use GPT-RAG v2.8.0, GPT-RAG Orchestrator v2.8.0, or gpt-rag-ui v2.8.0).
  • MANDATORY for EVERY GPT-RAG umbrella release — no exceptions. The published GitHub Release notes (the gh release create / gh release edit body, NOT just the CHANGELOG.md) MUST include a ## Component versions section with a Markdown table listing every validated runtime component from manifest.json components[] plus infra / AI Landing Zone from manifest.json ailz_tag. This is required even for a patch release where only the landing-zone pin changed and the runtime component versions are unchanged — always restate the full validated combination so operators see the exact set without cross-referencing other releases.
  • Read the versions directly from manifest.json at release time (tag for each entry in components[], and ailz_tag for the landing zone). Do not hand-copy from a previous release.
  • Place the ## Component versions table immediately after the ## Changed section and before ## Validation, matching the existing published releases (e.g. v2.8.0, v2.8.1).
  • The same table is ALSO added to CHANGELOG.md under the release heading (as the ### Validation component table). The GitHub Release notes and the changelog must agree.

Read the full file on GitHub · 241 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. 2mo ago First seen · 241 lines · 1,899 tokens per session scan A d6cbeff1b231

Subscribe to this mod's changes

GPT-RAG copilot-instructions.md is an instructions file published in the GitHub repository Azure/GPT-RAG (1,179 stars, last pushed 1mo ago), licensed MIT. It adds 1,899 tokens to every session, about $0.0076 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.

Git and workflowPlanningagent-frameworkagentic-ragazd-templatesazuregpt-4openai
Related

GPT-RAG copilot-instructions.md compared with instructions from other repositories

GPT-RAG copilot-instructions.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
GPT-RAG copilot-instructions.mdAzure/GPT-RAGInstructions file1.2k1mo agoMITA1,899GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode