ai-dev-gallery: Instructions file for GitHub Copilot

.github/instructions/adding-scenarios.instructions.md

ai-dev-gallery adding-scenarios.instructions.md is an instructions file for GitHub Copilot from microsoft/ai-dev-gallery. It costs 720 tokens per session, scanned A, original, MIT.

Repository instructions for microsoft/ai-dev-gallery, including the format of scenario and prompt-template files. A source generator is a build step that turns these files into program code.

In plain words
What is it for?
Use when adding or editing sample scenarios, categories, or prompt templates. It helps keep display names, unique IDs, descriptions, instructions, and icons in the expected structure.
Why use it?
Changes to the JSON files do not appear when the app is running until the project is fully rebuilt. The instructions also clarify which scenario fields are required and which are optional.

Instructions file for GitHub Copilot ✓ vendor

Written for GitHub Copilot: a Copilot instructions file.

This is microsoft/ai-dev-gallery's own configuration. It tells GitHub Copilot how to work on ai-dev-gallery 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 ai-dev-gallery configures →

About the project

AI Dev Gallery is an open-source Windows application that teaches developers how to add AI features using local models and APIs. Windows developers use its interactive samples to explore models and export C# Visual Studio projects.

microsoft/ai-dev-gallery · 1,515 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to microsoft/ai-dev-gallery. 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/microsoft/ai-dev-gallery/main/.github/instructions/adding-scenarios.instructions.md
Clone the repo
git clone --depth 1 https://github.com/microsoft/ai-dev-gallery

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 ai-dev-gallery adding-scenarios.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/microsoft/ai-dev-gallery/adding-scenarios/github.svg)](https://agentmods.dev/instructions/microsoft/ai-dev-gallery/adding-scenarios)
Your own site
<a href="https://agentmods.dev/instructions/microsoft/ai-dev-gallery/adding-scenarios"><img src="https://agentmods.dev/badge/instructions/microsoft/ai-dev-gallery/adding-scenarios/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 ai-dev-gallery adding-scenarios.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/microsoft/ai-dev-gallery/adding-scenarios"><img src="https://agentmods.dev/badge/instructions/microsoft/ai-dev-gallery/adding-scenarios.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 720 This file is loaded in full into every session.
When invoked 720 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.00720 $0.00720
Opus 5.5 $0.00288 $0.00288
Sonnet 5.5 $0.00144 $0.00144
Haiku 4.5 $0.00072 $0.00072

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

Security

Grade A, and why

ai-dev-gallery adding-scenarios.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/instructions/adding-scenarios.instructions.md · 103 lines

How it starts

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

Scenario and Prompt Template Instructions

When reviewing or modifying scenarios.json or promptTemplates.json:

IMPORTANT: Source Generator Embedded Files

Both scenarios.json and promptTemplates.json are embedded at build time by Roslyn source generators. Changes to these files require a full rebuild to take effect - they are NOT loaded dynamically at runtime.

scenarios.json Structure

{
  "CategoryName": {
    "Name": "Category Display Name",
    "Icon": "\uE8BD",
    "Description": "Category description for the UI",
    "Scenarios": {
      "ScenarioName": {
        "Name": "Scenario Display Name",
        "Description": "What this scenario does",
        "Instructions": "User-facing instructions for using this sample",
        "Id": "kebab-case-unique-id",
        "Icon": "\uE8D4"
      }
    }
  }
}

Required Scenario Fields

  • Name: Display name shown in UI
  • Id: Unique kebab-case identifier (e.g., "summarize-text")

Optional Fields

  • Description: Brief description of the scenario
  • Instructions: User instructions for the sample UI
  • Icon: Segoe MDL2 glyph code (e.g., "\uE8BD")

Usage in Samples

The ScenarioType enum is auto-generated from scenarios.json. Reference in [GallerySample]:

[GallerySample(
    Scenario = ScenarioType.TextSummarizeText,  // CategoryScenarioName format
    ...
)]

The naming pattern is {Category}{ScenarioName} in PascalCase.

promptTemplates.json Structure

{
  "TemplateName": {
    "system": "<|system|>\n{{CONTENT}}<|end|>\n",
    "user": "<|user|>\n{{CONTENT}}<|end|>\n",
    "assistant": "<|assistant|>\n{{CONTENT}}<|end|>\n",
    "stop": ["<|end|>", "<|user|>"]
  }
}

Required Prompt Template Fields

  • user: Template for user messages with {{CONTENT}} placeholder
  • stop: Array of stop sequences

Optional Prompt Template Fields

  • system: Template for system prompt with {{CONTENT}} placeholder
  • assistant: Template for assistant responses with {{CONTENT}} placeholder

Read the full file on GitHub · 103 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 · 103 lines · 720 tokens per session scan A 4d921837ee1b

Subscribe to this mod's changes

ai-dev-gallery adding-scenarios.instructions.md is an instructions file published in the GitHub repository microsoft/ai-dev-gallery (1,515 stars, last pushed 12d ago), licensed MIT. It adds 720 tokens to every session, about $0.0029 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.