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.
npx agentmods add instructions/ukho/ukho.githubcopilot.toolkit/authgit clone --depth 1 https://github.com/UKHO/UKHO.GitHubCopilot.ToolKitWhat 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 | $0.00813 | $0.00813 |
| Opus 5 | $0.00407 | $0.00407 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
UKHO.GitHubCopilot.ToolKit auth.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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standards-based authentication guidance
Overview
These instructions standardize how authentication guidance should be written and implemented for Microsoft projects. Application code should focus on standards-based integration such as OpenID Connect (OIDC) and OAuth 2.0 so that identity-provider choices can vary by environment while remaining compatible with Microsoft-hosted solutions.
Scope
Applies to: src/**/AppHost/**/*, src/**/*AppHost*.csproj, src/**/*.cs, src/**/*.csproj, src/**/*.json
- Applies when adding or changing authentication for APIs, web apps, services, or local orchestration.
- This is additive to more specific stack instructions when those files exist.
Instructions
MUST
-
Keep identity-provider selection environment-driven.
- Document which provider is used in each environment when that choice matters.
- Prefer configuration-based selection so application code does not need environment-specific branching for provider swaps.
-
For Azure-hosted Microsoft solutions, prefer Microsoft Entra ID when it satisfies the project requirements.
- When integrating ASP.NET Core apps or APIs with Entra ID, prefer supported Microsoft libraries such as
Microsoft.Identity.Webwhere appropriate.
- When integrating ASP.NET Core apps or APIs with Entra ID, prefer supported Microsoft libraries such as
-
Prefer standards-based integration in application code:
- Web apps MUST use OIDC Authorization Code flow (with PKCE where applicable).
- APIs MUST validate access tokens using OAuth 2.0 / JWT bearer authentication.
-
Keep identity configuration externalized.
- Authority/issuer URLs, tenant/realm, client IDs, and secrets MUST NOT be hard-coded.
- Secrets MUST NOT be checked into source control.
-
When a non-production identity provider is used for local development or isolated testing, keep that choice explicit in configuration and documentation.
- If the repository uses container orchestration or other managed local infrastructure for identity, manage the provider through that setup rather than undocumented manual steps.
- Keep local identity setup repeatable so developers can recreate realms, tenants, applications, or client registrations consistently.
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.
- yesterday First seen · 75 lines · 813 tokens per session scan A 6eebe5f80f65
UKHO.GitHubCopilot.ToolKit auth.instructions.md is an instructions file published in the GitHub repository UKHO/UKHO.GitHubCopilot.ToolKit (1 stars, last pushed 2mo ago), licensed MIT. It adds 813 tokens to every session, about $0.0041 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain 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.