What is UKHO.GitHubCopilot.ToolKit docs.instructions.md?

Repository instructions for writing Markdown documentation under the docs directory. Markdown is plain text with simple formatting such as headings, links, and code blocks.

Use them when adding, editing, moving, or renaming Markdown documentation files.

They keep documentation consistent, readable, and easy to navigate as it changes over time.

UKHO.GitHubCopilot.ToolKit docs.instructions.md

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/ukho/ukho.githubcopilot.toolkit/docs

Clone the repo

git clone --depth 1 https://github.com/UKHO/UKHO.GitHubCopilot.ToolKit

Made for: GitHub Copilot.

Per session 857 This file is loaded in full into every session.

When invoked 857 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.

Model	Per session	Once invoked
Fable 5	$0.00857	$0.00857
Opus 5	$0.00428	$0.00428
Sonnet 5	$0.00171	$0.00171
Haiku 4.5	$0.00086	$0.00086

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

Security

Grade A, and why

UKHO.GitHubCopilot.ToolKit docs.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/docs.instructions.md · 73 lines

How it starts

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

Documentation authoring rules (docs)

Overview

These instructions define how to create and maintain documentation under ./docs/. They are for contributors who add, update, move, or rename documentation.

Scope

Applies to: docs/**/*.md

These rules cover document structure, Markdown conventions, linking, and maintenance expectations.
When multiple instruction files apply, prefer the more specific scope.

Instructions

MUST

Create documentation under ./docs/ as Markdown files with the .md extension.
Use semantic Markdown structure with ATX headings (# style).
Include one (and only one) H1 (#) heading per file.
Make the H1 the first content in the file.
Use heading levels in order (do not skip levels, for example, from H2 to H4).
Use fenced code blocks for code samples and specify the language (for example, csharp, json, xml, bash, powershell).
Use descriptive link text that explains the target (use the page title or meaningful nouns/verbs).
Use https links where the target supports it.
When linking to learn.microsoft.com, omit locale segments (for example, do not include /en-us/ in the URL).
When linking to other repo files, prefer relative links and use forward slashes (/) in link paths.
Provide meaningful alt text for images using Markdown image syntax (![alt text](path)).
When you move or rename documentation files, update inbound and outbound links so navigation remains correct.
Review the relevant pages under ./docs/wiki/ before drafting planning documents, workflow guidance, or project updates that rely on repository context.
When completed plan work changes the implemented solution, update the relevant pages under ./docs/wiki/ before the plan is considered complete.
When any documentation, prompt, agent, template, or workflow change affects project understanding, workflow sequencing, implementation guidance, or usage guidance, update the relevant pages under ./docs/wiki/ before the task is considered complete.
When ./docs/wiki/ pages are updated, ensure the affected navigation and cross-links continue to resolve.

Read the full file on GitHub · 73 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.

yesterday First seen · 73 lines · 857 tokens per session scan A 1deb971b2735

Subscribe to this mod's changes

UKHO.GitHubCopilot.ToolKit docs.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 857 tokens to every session, about $0.0043 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.

Writing and docs

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens