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/prompts.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/prompts)<a href="https://agentmods.dev/instructions/ukho/ukho.githubcopilot.toolkit/prompts"><img src="https://agentmods.dev/badge/instructions/ukho/ukho.githubcopilot.toolkit/prompts/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/prompts"><img src="https://agentmods.dev/badge/instructions/ukho/ukho.githubcopilot.toolkit/prompts.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.00804 | $0.00804 |
| Opus 5.5 | $0.00322 | $0.00322 |
| Sonnet 5.5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
UKHO.GitHubCopilot.ToolKit prompts.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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot prompt naming rules
Overview
These instructions define how to name and describe Copilot prompt files in this repository. They help contributors keep prompt assets brief, consistent, and easy to understand from the file name and front matter alone.
Scope
Applies to: .github/prompts/**/*.prompt.md
- Applies when creating, renaming, or substantially restructuring prompt files under
./.github/prompts/. - Does not apply to non-prompt markdown files that do not use the
*.prompt.mdnaming pattern.
Instructions
MUST
- Name prompt files using lowercase kebab-case.
- Name prompt files using the pattern
<verb>-<subject>[-<qualifier>].prompt.md. - Start prompt file names with a clear action verb that describes the primary task the prompt performs.
- Use a subject that identifies the main artifact, outcome, or target of the prompt.
- Keep the front matter
namefield aligned with the file name stem.- Example:
create-instructions.prompt.mdMUST usename: create-instructions.
- Example:
- Ensure the file name, front matter
name, and prompt purpose describe the same outcome. - Keep prompt names brief enough to scan quickly while still distinguishing the prompt from nearby files.
- Use front matter
descriptionto state the prompt's intended outcome in one clear sentence.
SHOULD
- Prefer prompt names with two to four terms before the
.prompt.mdsuffix. - Prefer a controlled verb set such as
create,update,review,analyse,generate,refactor,validate,summarise, ortroubleshootwhen those verbs match the intended task. - Add a qualifier only when it materially improves distinction.
- Examples:
security,playwright,csharp,edge-cases.
- Examples:
- Prefer folder structure to carry broad categorization so file names can stay focused on the prompt's specific purpose.
- Use the shortest subject wording that remains unambiguous within the prompts folder.
- When a prompt defines a planning or project-update workflow, prefer explicit instructions that tell contributors to review relevant
docs/wiki/pages before proceeding and to refresh the wiki after any resulting change.
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 · 72 lines · 804 tokens per session scan A f4b5ba916bce
UKHO.GitHubCopilot.ToolKit prompts.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 804 tokens to every session, about $0.0032 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
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.