ai-dev-gallery adding-sharedcode.instructions.md

Instructions for reusable C# and XAML code shared by multiple samples in Microsoft’s AI developer gallery. The code must work independently of the main app and be exportable into standalone Visual Studio projects.

In plain words
What is it for?
Adding reusable sample utilities, checking dependencies and public APIs, preparing code for export, and understanding generated SharedCodeEnum entries.
Why use it?
They prevent shared utilities from depending on pages, view models, paths, or packages that exported samples will not have. They also explain how shared-code names are generated.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/microsoft/ai-dev-gallery/adding-sharedcode
Clone the repo
git clone --depth 1 https://github.com/microsoft/ai-dev-gallery

Made for: GitHub Copilot.

Per session 494 This file is loaded in full into every session.
When invoked 494 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00494 $0.00494
Opus 5 $0.00247 $0.00247
Sonnet 5 $0.00099 $0.00099
Haiku 4.5 $0.00049 $0.00049

Measured yesterday against content hash ef6830ffb858, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ai-dev-gallery adding-sharedcode.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 yesterday.

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-sharedcode.instructions.md · 76 lines

How it starts

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

SharedCode Instructions

When reviewing or modifying code in AIDevGallery/Samples/SharedCode/:

Purpose

SharedCode contains reusable utilities that are:

  1. Used by multiple samples within the app
  2. Exported with samples when users generate standalone VS projects

Because SharedCode is exported, it has special requirements.

Code Requirements

Must Be Self-Contained

  • Minimize dependencies on app-specific code
  • Use only packages specified in sample's NugetPackageReferences
  • Avoid references to AIDevGallery.Pages, AIDevGallery.ViewModels, etc.

Must Be Exportable

  • No internal app state dependencies
  • No hardcoded paths to app resources
  • Clear, documented public APIs

SharedCodeEnum Auto-Generation

The SharedCodeEnum is auto-generated by the source generator from:

  • Files in AIDevGallery/Samples/SharedCode/ directory
  • Special case: AIDevGallery/Utils/DeviceUtils.cs
  • Special case: NativeMethods.txt (for P/Invoke definitions)

Generation rules:

  • Each .cs file becomes an enum value
  • XAML pairs (.xaml + .xaml.cs) get both *Cs and *Xaml values

Example: BitmapFunctions.csSharedCodeEnum.BitmapFunctions

Usage in Samples

Reference in [GallerySample] attribute:

[GallerySample(
    SharedCode = [
        SharedCodeEnum.BitmapFunctions,
        SharedCodeEnum.ImageNetLabels,
        SharedCodeEnum.Prediction
    ],
    NugetPackageReferences = [
        "System.Drawing.Common"
    ],
    ...
)]

Adding New SharedCode

  1. Create file in appropriate subfolder
  2. Ensure file is self-contained
  3. Rebuild to generate new SharedCodeEnum value
  4. Update samples that use the code
  5. Document required NuGet packages

Code Review Checks

  • New SharedCode files follow naming conventions
  • Required NuGet packages documented
  • No app-specific dependencies
  • Code compiles standalone (for export)
  • Proper error handling for edge cases
  • Comments explain non-obvious logic
  • Matching .xaml files for any XAML controls

Read the full file on GitHub · 76 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. yesterday First seen · 76 lines · 494 tokens per session scan A ef6830ffb858

Subscribe to this mod's changes

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