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.
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.
curl -O https://raw.githubusercontent.com/microsoft/ai-dev-gallery/main/.github/instructions/adding-sharedcode.instructions.mdgit clone --depth 1 https://github.com/microsoft/ai-dev-galleryWrote 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/microsoft/ai-dev-gallery/adding-sharedcode)<a href="https://agentmods.dev/instructions/microsoft/ai-dev-gallery/adding-sharedcode"><img src="https://agentmods.dev/badge/instructions/microsoft/ai-dev-gallery/adding-sharedcode/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/microsoft/ai-dev-gallery/adding-sharedcode"><img src="https://agentmods.dev/badge/instructions/microsoft/ai-dev-gallery/adding-sharedcode.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.00494 | $0.00494 |
| Opus 5.5 | $0.00198 | $0.00198 |
| Sonnet 5.5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
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 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.
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:
- Used by multiple samples within the app
- 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
.csfile becomes an enum value - XAML pairs (
.xaml+.xaml.cs) get both*Csand*Xamlvalues
Example: BitmapFunctions.cs → SharedCodeEnum.BitmapFunctions
Usage in Samples
Reference in [GallerySample] attribute:
[GallerySample(
SharedCode = [
SharedCodeEnum.BitmapFunctions,
SharedCodeEnum.ImageNetLabels,
SharedCodeEnum.Prediction
],
NugetPackageReferences = [
"System.Drawing.Common"
],
...
)]
Adding New SharedCode
- Create file in appropriate subfolder
- Ensure file is self-contained
- Rebuild to generate new
SharedCodeEnumvalue - Update samples that use the code
- 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
.xamlfiles for any XAML controls
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.
- 2mo ago First seen · 76 lines · 494 tokens per session scan A ef6830ffb858
ai-dev-gallery adding-sharedcode.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 494 tokens to every session, about $0.0020 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.
Other instructions, from other repositories
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core 10, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
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).
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.