Borrowing it
Nothing to install: this file belongs to WhatIfWeDigDeeper/agent-skills. 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/WhatIfWeDigDeeper/agent-skills/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/WhatIfWeDigDeeper/agent-skillsWrote 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/whatifwedigdeeper/agent-skills/copilot-instructions)<a href="https://agentmods.dev/instructions/whatifwedigdeeper/agent-skills/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/whatifwedigdeeper/agent-skills/copilot-instructions.svg" alt="Measured on agentmods" 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.11925 | $0.11925 |
| Opus 5 | $0.05962 | $0.05962 |
| Sonnet 5 | $0.02385 | $0.02385 |
| Haiku 4.5 | $0.01192 | $0.01192 |
Grade A, and why
agent-skills copilot-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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agent-skills CLAUDE.md — 86% identical, 291 lines differ
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions
Keep CLAUDE.md in sync: whenever you add, update, or remove a rule in this file, apply the equivalent change to the appropriate CLAUDE.md — the root CLAUDE.md for repo-wide rules, or a subdirectory CLAUDE.md (e.g. skills/CLAUDE.md, evals/CLAUDE.md, tests/CLAUDE.md, specs/CLAUDE.md) for context-specific rules (skill authoring, eval benchmarks, test conventions, spec editing). Claude Code auto-loads subdirectory CLAUDE.md files when working in those directories; Copilot has only one instructions file, so all rules — including those whose canonical home is a subdirectory CLAUDE.md — must also appear here; a rule dropped from a CLAUDE.md because a subdirectory CLAUDE.md covers it stays here. The two assistants (Copilot vs. Claude Code) should encode the same project conventions. When running /learn in this project, always update both the appropriate CLAUDE.md and .github/copilot-instructions.md without asking which to update. The instruction-sync CI check enforces this pairing for any CLAUDE.md path in the repo — it does not compare the two files' content.
Project Overview
Evals belong under evals/ at the repo root, not inside skill directories — they are development artifacts and should not be bundled when a skill is distributed.
Core Editing Rules
- Keep instructions assistant-neutral unless a tool or platform detail is inherently assistant-specific.
- Skill description has a 500-character hard limit — the
descriptionfield in SKILL.md frontmatter is capped at 500 characters by the skills runtime. Keep descriptions concise; count characters before finalizing. - Preserve the existing workflow style in
SKILL.md: numbered process sections, executable bash blocks, tables where useful, and examples where useful. - When substantially modifying a skill, update its
README.mdentry and notes. - Bump
metadata.versionon everySKILL.mdchange or reference-file change that affects the skill. - On an active PR branch, re-run the check below before committing any
SKILL.mdchange — not just when you intend to bump — to confirm no bump already exists relative toorigin/main:
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.
- 7d ago First seen · 232 lines · 11,925 tokens per session scan E e54390dbf0f7
agent-skills copilot-instructions.md is an instructions file published in the GitHub repository WhatIfWeDigDeeper/agent-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 11,925 tokens to every session, about $0.0596 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.
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.
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.
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 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
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.