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 skills/ikcode-dev/copilot-kit/kit-copilot-create-instructionnpx skills add ikcode-dev/copilot-kit --skill kit-copilot-create-instructiongit 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.00069 | $0.02431 |
| Opus 5 | $0.00034 | $0.01215 |
| Sonnet 5 | $0.00014 | $0.00486 |
| Haiku 4.5 | $0.00007 | $0.00243 |
Grade A, and why
kit-copilot-create-instruction 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 2d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Granular Copilot Instructions
What This Skill Does
Creates properly structured granular instruction files (.instructions.md) for GitHub Copilot in VS Code following the custom instructions documentation. These files provide targeted, file-type-specific guidance that activates only when Copilot is working with matching files.
Granular instructions are the conditional layer of Copilot customization — they complement the universal .github/copilot-instructions.md by adding context-specific conventions that would be too verbose or irrelevant in the core file.
Key Concepts: Granular Instructions vs Other Customizations
Understanding the separation of concerns is critical for effective granular instructions. Each customization mechanism has a distinct purpose:
| Component | Defines | Analogy | File Type |
|---|---|---|---|
| Core Instructions | Universal project context for ALL interactions | The company handbook | .github/copilot-instructions.md |
| Granular Instructions | Context-specific conventions for MATCHING files | Department-specific guidelines | .github/instructions/*.instructions.md |
| Custom Agent | WHO the AI is and HOW it behaves | The employee's role and personality | .agent.md |
| Agent Skill | Reusable CAPABILITY or multi-step workflow | A specialized training module | SKILL.md in a skill directory |
| Prompt File | WHAT specific task to perform | A work order or task assignment | .prompt.md |
The Layered Instruction Architecture
GitHub Copilot supports a layered approach to custom instructions:
- Core layer (
.github/copilot-instructions.md) — Attached to EVERY Copilot conversation. Contains universal project context. - Granular layer (
.github/instructions/*.instructions.md) — Applied conditionally viaapplyToglob patterns. Contains targeted, context-specific guidance.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 204 lines · 69 tokens per session scan A 15aef4f65d66
kit-copilot-create-instruction is a skill published in the GitHub repository ikcode-dev/copilot-kit (29 stars, last pushed 5mo ago), licensed MIT. It adds 69 tokens to every session and 2,431 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…