Borrowing it
Nothing to install: this file belongs to UKHO/UKHO.GitHubCopilot.ToolKit. 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/UKHO/UKHO.GitHubCopilot.ToolKit/main/.github/instructions/dotnet-stack.instructions.mdgit clone --depth 1 https://github.com/UKHO/UKHO.GitHubCopilot.ToolKitWrote 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/ukho/ukho.githubcopilot.toolkit/dotnet-stack)<a href="https://agentmods.dev/instructions/ukho/ukho.githubcopilot.toolkit/dotnet-stack"><img src="https://agentmods.dev/badge/instructions/ukho/ukho.githubcopilot.toolkit/dotnet-stack/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/ukho/ukho.githubcopilot.toolkit/dotnet-stack"><img src="https://agentmods.dev/badge/instructions/ukho/ukho.githubcopilot.toolkit/dotnet-stack.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.01296 | $0.01296 |
| Opus 5.5 | $0.00518 | $0.00518 |
| Sonnet 5.5 | $0.00259 | $0.00259 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
UKHO.GitHubCopilot.ToolKit dotnet-stack.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 1mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsoft stack .NET architecture guidelines
Overview
These instructions define baseline default technical choices and architectural expectations for repositories that use the Microsoft .NET stack. Apply this guidance only when the target project is actually using .NET application technologies covered by this file.
Scope
Applies to: src/**/*.cs, src/**/*.csproj, src/**/*.sln, src/**/*.razor, src/**/*.json, infra/**/*
- Applies when creating new services, APIs, .NET web front ends, or distributed application wiring.
- Applies when selecting a database or local orchestration approach for a work item.
- The stack choices in this file are defaults for applicable .NET work, not absolute mandates for every project shape.
- When a work item needs a justified deviation from these defaults, document the reason in the relevant project or work-package documentation so the deviation remains reviewable.
- For project-specific UI component guidance, also follow any applicable scoped instruction files.
Instructions
MUST
-
Use C# and the repository’s configured .NET SDK/runtime version (follow
global.jsonif present; otherwise check Microsoft Learn to confirm the latest .NET LTS version and target it by default). -
Enable nullable reference types for new .NET projects (
<Nullable>enable</Nullable>) and treat new nullable warnings as errors in touched projects when feasible. -
For new HTTP services, prefer Minimal APIs unless a concrete requirement needs an alternative.
-
When exposing HTTP endpoints, provide OpenAPI output (for example via
Microsoft.AspNetCore.OpenApi) and include health endpoints.- OpenAPI SHOULD be mapped only in the
Developmentenvironment unless explicitly required. - Health endpoints SHOULD include separate readiness and liveness probes when the service has dependencies.
- OpenAPI SHOULD be mapped only in the
-
For new .NET web UIs, prefer Blazor when it fits the project’s established technology direction.
-
Prefer a Microsoft-aligned data platform choice when the project requires a relational data store.
-
Use a migration-based schema workflow when the chosen persistence technology supports it.
-
Keep all connection strings and credentials out of source control; use configuration + secret injection (development user-secrets; production secret store/managed identity where applicable).
-
Follow
/.github/instructions/configuration.instructions.mdfor operator-managed configuration storage and secret-handling flows.
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.
- 1mo ago First seen · 106 lines · 1,296 tokens per session scan A 1161036f55ef
UKHO.GitHubCopilot.ToolKit dotnet-stack.instructions.md is an instructions file published in the GitHub repository UKHO/UKHO.GitHubCopilot.ToolKit (1 stars, last pushed 4mo ago), licensed MIT. It adds 1,296 tokens to every session, about $0.0052 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-31.
Other instructions, from other repositories
graftcode graftcode-dotnet.instructions.md
Instructions for grft-dev/graftcode, covering graftcode — .net backend services, when this applies (always), authoritative docs (source of truth), golden rules and service = .net class library.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).