What is Hook Naming Conventions?

A naming rule for Copilot hook configuration files in the copilot-kit project.

Use it when creating or renaming a hook configuration file so its name follows the required kit-purpose pattern.

Consistent filenames make hook configurations easier to recognize, locate, and validate.

How ikcode-dev/copilot-kit configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to ikcode-dev/copilot-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ikcode-dev/copilot-kit/main/.github/instructions/hook-naming.instructions.md

Clone the repo

git clone --depth 1 https://github.com/ikcode-dev/copilot-kit

Made for: GitHub Copilot.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ikcode-dev/copilot-kit/hook-naming/github.svg)](https://agentmods.dev/instructions/ikcode-dev/copilot-kit/hook-naming)

Your own site

<a href="https://agentmods.dev/instructions/ikcode-dev/copilot-kit/hook-naming"><img src="https://agentmods.dev/badge/instructions/ikcode-dev/copilot-kit/hook-naming/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ikcode-dev/copilot-kit/hook-naming"><img src="https://agentmods.dev/badge/instructions/ikcode-dev/copilot-kit/hook-naming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 523 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00523	$0.00523
Opus 5.5	$0.00209	$0.00209
Sonnet 5.5	$0.00105	$0.00105
Haiku 4.5	$0.00052	$0.00052

Measured 2mo ago against content hash e90063a85f8b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Hook Naming Conventions 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 2mo 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.

.github/instructions/hook-naming.instructions.md · 54 lines

How it starts

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

Hook Naming Conventions for copilot-kit

Apply these rules when creating a new Copilot hook configuration file or when a hook config rename is explicitly in scope.

Naming Pattern

New or renamed hook config files in this repository must use this filename pattern:

kit-{hook-purpose}(-{qualifier})*.json

Rollout Boundary

Anti-Patterns

Validation

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

2mo ago First seen · 54 lines · 523 tokens per session scan A e90063a85f8b

Subscribe to this mod's changes

Hook Naming Conventions is an instructions file published in the GitHub repository ikcode-dev/copilot-kit (29 stars, last pushed 7mo ago), licensed MIT. It adds 523 tokens to every session, about $0.0021 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-30.

Hook Naming Conventions next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
Hook Naming Conventionsikcode-dev/copilot-kit	Instructions file	29	7mo ago	MIT	A	523	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

copilot-kit: Instructions file for GitHub Copilot