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/folders.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/folders)<a href="https://agentmods.dev/instructions/ukho/ukho.githubcopilot.toolkit/folders"><img src="https://agentmods.dev/badge/instructions/ukho/ukho.githubcopilot.toolkit/folders/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/folders"><img src="https://agentmods.dev/badge/instructions/ukho/ukho.githubcopilot.toolkit/folders.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.00619 | $0.00619 |
| Opus 5.5 | $0.00248 | $0.00248 |
| Sonnet 5.5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
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 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 — 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/, andtest/. 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 undertest/(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.mdand*.templates.md) under./.github/templates/. -
Verify the target folder exists (or locate it) before creating any new
*.instructions.mdor*.prompt.mdfile. -
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, orCommonroot) 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.
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 · 55 lines · 619 tokens per session scan A cce877a155e5
UKHO.GitHubCopilot.ToolKit folders.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 619 tokens to every session, about $0.0025 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.