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.
npx agentmods add instructions/ikcode-dev/copilot-kit/skill-naminggit clone --depth 1 https://github.com/ikcode-dev/copilot-kitWhat 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.01239 | $0.01239 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
Skill 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 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Naming Conventions for copilot-kit
These conventions ensure skills from this repository are instantly identifiable when mixed with project-specific skills in the VS Code / command palette.
Naming Pattern
All skills in this repository must follow:
kit-{category}-{verb}-{object}
| Segment | Purpose | Examples |
|---|---|---|
kit- |
Origin prefix — identifies the skill as coming from copilot-kit |
Always kit- |
{category} |
Domain grouping | copilot, sdd |
{verb} |
Action the skill performs | create, check, implement, review |
{object} |
Target of the action | agent, skill, hook, spec, conformance |
Why kit-?
ck-— too cryptic, not recognizable at a glancecopilot-kit-— too long, wastes the 64-charnamelimitkit-— 4 chars, filters all copilot-kit skills together when typing/kit-
Categories
| Category | Scope |
|---|---|
copilot |
Skills related to Copilot customization (agents, skills, hooks, instructions, prompts) |
sdd |
Skills related to Spec-Driven Development workflows (specs, conformance checks, implementation) |
New categories follow the same pattern: short, lowercase, hyphenated.
Directory Structure
The name field in SKILL.md frontmatter must match the parent directory name. Intermediate grouping directories (copilot/, sdd/) are for filesystem organization only:
.github/skills/
copilot/
kit-copilot-create-agent/SKILL.md
kit-copilot-create-skill/SKILL.md
sdd/
kit-sdd-create-spec/SKILL.md
kit-sdd-check-conformance/SKILL.md
SKILL.md Frontmatter Requirements
---
name: kit-{category}-{verb}-{object} # must match directory name
description: "A skill that [verb]s [object] for [context]. Use when [trigger scenario]."
argument-hint: Describe what input to provide
user-invocable: true
disable-model-invocation: false
---
descriptionshould explain both what the skill does and when to use it so Copilot's progressive disclosure loads it automatically at the right time.- Keep
nameunder 64 characters (the spec maximum).
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 · 121 lines · 1,239 tokens per session scan A a0f336651d00
Skill Naming Conventions is an instructions file published in the GitHub repository ikcode-dev/copilot-kit (29 stars, last pushed 5mo ago), licensed MIT. It adds 1,239 tokens to every session, about $0.0062 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-30.
Other instructions, from other repositories
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.
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).
next.js 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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain 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.