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/tests.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/tests)<a href="https://agentmods.dev/instructions/ukho/ukho.githubcopilot.toolkit/tests"><img src="https://agentmods.dev/badge/instructions/ukho/ukho.githubcopilot.toolkit/tests/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/tests"><img src="https://agentmods.dev/badge/instructions/ukho/ukho.githubcopilot.toolkit/tests.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.01340 | $0.01340 |
| Opus 5.5 | $0.00536 | $0.00536 |
| Sonnet 5.5 | $0.00268 | $0.00268 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
UKHO.GitHubCopilot.ToolKit tests.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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test approach (unit, integration, E2E, functional)
Overview
These instructions define how automated tests are structured and authored in this repository. Prefer fast, isolated unit tests. Add integration and end-to-end tests for cross-boundary behavior where needed. Add functional tests to validate documented requirements. The framework and suite-shape choices in this file are repository defaults unless a documented exception applies.
Scope
Applies to: test/**/*.cs, test/**/*.csproj
- Applies when creating or updating any test projects or test code under
test/. - The framework and structure choices in this file are defaults for repository test work unless a narrower file or an explicitly documented exception applies.
- 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.
- These rules are additive to:
/.github/instructions/folders.instructions.md/.github/instructions/playwright.instructions.md/.github/instructions/work-packages.instructions.md
Instructions
MUST
-
Keep all automated tests under
test/. -
Use xUnit for unit test projects by default.
-
All new non-trivial code MUST be covered with unit tests.
- Where legacy code, generated code, boilerplate, or other constraints make unit testing impractical, any exclusion MUST be a conscious and reviewable team decision.
-
Prefer unit tests over higher-level tests when a behavior can be validated without infrastructure.
-
Standardize test project structure as:
test/<Service>/<Service>.<TestType>/...- Use separate projects per test type so suites can be run independently:
test/<Service>/<Service>.UnitTeststest/<Service>/<Service>.IntegrationTeststest/<Service>/<Service>.E2ETeststest/<Service>/<Service>.FunctionalTests
- Use separate projects per test type so suites can be run independently:
-
Use descriptive test file names that match the contained test class; avoid generic names like
UnitTest1.cs. -
Automated test method names MUST follow the
MethodName_StateUnderTest_ExpectedResultconvention.- Prefer names that read as natural English, typically using
Should...for the expected result andWhen...for the state under test. - Example:
CalculateTotal_ShouldReturnZero_WhenCartIsEmpty
- Prefer names that read as natural English, typically using
-
Automated tests MUST be fully documented with comments immediately above each test method.
- Test comments MUST capture requirement traceability when applicable, using identifiers from the relevant work package or requirement source (for example
FR1,NF2,SR3,TR1). - Test comments MUST explain what the test is verifying, the expected outcome, and why the behavior matters or regression risk it is guarding against.
- When the scenario is not obvious from the method name alone, test comments MUST also explain important setup assumptions or boundary conditions.
- Prefer XML documentation comments (
///) when the language and test framework support them cleanly.
- Test comments MUST capture requirement traceability when applicable, using identifiers from the relevant work package or requirement source (for example
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 · 110 lines · 1,340 tokens per session scan A ec36a8a5a88d
UKHO.GitHubCopilot.ToolKit tests.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,340 tokens to every session, about $0.0054 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.