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/configurationgit 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.00469 | $0.00469 |
| Opus 5 | $0.00234 | $0.00234 |
| Sonnet 5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
UKHO.GitHubCopilot.ToolKit configuration.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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration management
Overview
These instructions define how operator-managed configuration and secrets are handled in a Microsoft project. The goal is to keep runtime settings centralized, protect sensitive values, and ensure configuration changes flow through the intended project experience.
Scope
Applies to: src/**/*.cs, src/**/*.csproj, src/**/*.json, src/**/*.razor, infra/**/*
- Applies when adding or changing configuration storage, configuration editing flows, secret handling, or admin or operator UI features.
- Applies to backend services, UI components, automation, and infrastructure that support operator-managed configuration.
Instructions
MUST
- Store operator-managed configuration in the project’s chosen authoritative configuration store.
- Keep third-party credentials and similar secrets securely protected at rest and in transit.
- Manage operator-facing configuration updates through the approved project experience when the repository exposes configuration management features.
- Use write-only secret handling for operator-managed secrets:
- Operators MAY set or replace a secret.
- Stored secret values MUST NOT be displayed back to the operator after save.
- APIs and UI models MUST avoid returning populated secret values once persisted.
- Keep secrets and connection details out of source control.
- Use explicit application services or repositories for configuration persistence rather than scattering configuration writes across unrelated UI, endpoint, or automation code.
SHOULD
- Separate secret metadata from secret material when it improves maintainability or auditing.
- Prefer audit-friendly configuration update flows so operational changes can be traced when the application supports it.
- Keep configuration editing experiences focused on changing current settings without exposing existing secret values.
MUST NOT
- MUST NOT render existing secret values in UI forms, API responses, logs, exceptions, or diagnostics.
- MUST NOT store plaintext secrets in source control or sample configuration files.
- MUST NOT bypass the approved configuration workflow with ad hoc operator-only processes unless an explicit requirement justifies it.
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 · 53 lines · 469 tokens per session scan A c5c2777c4589
UKHO.GitHubCopilot.ToolKit configuration.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 469 tokens to every session, about $0.0023 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.