Use them when creating, moving, or reorganizing code, tests, documentation, infrastructure, projects, Copilot instruction files, or Copilot prompt files.

They reduce misplaced files and gradual changes to the repository layout. They also require references to be updated when files move so builds and tests continue to work.

UKHO.GitHubCopilot.ToolKit folders.instructions.md

Q: What is UKHO.GitHubCopilot.ToolKit folders.instructions.md?

Repository instructions for keeping files and projects in a consistent folder structure.

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/folders

Clone the repo

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

Made for: GitHub Copilot.

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

When invoked 619 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.00619	$0.00619
Opus 5	$0.00309	$0.00309
Sonnet 5	$0.00124	$0.00124
Haiku 4.5	$0.00062	$0.00062

Measured yesterday against content hash cce877a155e5, 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 folders.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/folders.instructions.md · 55 lines

How it starts

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

Folder structure rules

Overview

These instructions keep the repository layout consistent by ensuring new files and new projects are added in the right place, and existing boundaries are not eroded over time.

Scope

These rules apply when creating new files or folders, moving files or folders, or introducing new projects.

Instructions

MUST

Preserve the current top-level folder layout; do not introduce new top-level folders without an explicit architectural reason.
When adding or reorganizing code, prefer the following top-level folders for this repository: .github/, docs/, infra/, src/, and test/. If some of these folders do not yet exist, create them as needed rather than introducing alternative top-level roots.
Prefer placing product code under src/ and automated tests under test/ (or the closest existing equivalent), creating those folders when necessary.
When moving files, update all references to preserve build/test viability (solution/project references, namespaces/imports, tooling paths).
Create Copilot instruction files (*.instructions.md) under ./.github/instructions/.
Create Copilot prompt files (*.prompt.md) under ./.github/prompts/.
Create template markdown files (*.template.md and *.templates.md) under ./.github/templates/.
Verify the target folder exists (or locate it) before creating any new *.instructions.md or *.prompt.md file.
Check for an existing shared location, reusable asset, or scoped file before creating a new parallel file or folder for similar guidance or functionality.

SHOULD

Mirror production structure in tests (or follow the established test layout) so mapping between code and tests is obvious.
Keep shared utilities in the established shared/common area rather than duplicating per feature.
Keep configuration files close to the component they configure unless the repository already centralizes that config type.

MUST NOT

MUST NOT create parallel duplicate roots (for example, a second Services, Core, or Common root) when an established location exists.
MUST NOT move files across layers without maintaining boundaries and updating references.
MUST NOT add new projects/solutions that bypass the repository's existing build/test orchestration.
MUST NOT create parallel near-duplicate instructions, prompts, templates, or shared code locations when an established reusable location already exists.

Read the full file on GitHub · 55 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 · 55 lines · 619 tokens per session scan A cce877a155e5

Subscribe to this mod's changes

UKHO.GitHubCopilot.ToolKit folders.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 619 tokens to every session, about $0.0031 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.

Data and AI Testing 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