Borrowing it
Nothing to install: this file belongs to GiladShoham/awesome-claude-plugins. 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/GiladShoham/awesome-claude-plugins/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/GiladShoham/awesome-claude-pluginsWrote 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/giladshoham/awesome-claude-plugins/copilot-instructions)<a href="https://agentmods.dev/instructions/giladshoham/awesome-claude-plugins/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/giladshoham/awesome-claude-plugins/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.01223 | $0.01223 |
| Opus 5 | $0.00611 | $0.00611 |
| Sonnet 5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
awesome-claude-plugins 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 8d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for Awesome Claude Plugins
This repository is a curated marketplace for Claude plugins, following the Claude Plugin Marketplace specification.
Repository Purpose
This is a plugin marketplace that provides a centralized location to discover and share Claude plugins. The repository contains:
- A marketplace metadata file (
marketplace.json) - Plugin definitions in the
plugins/directory - A plugin template for creating new plugins
- Validation scripts and CI/CD workflows
Plugin Structure
All plugins must follow this exact directory structure:
plugins/your-plugin-name/
├── .claude-plugin/ # Plugin configuration directory (required)
│ └── plugin.json # Plugin metadata in JSON format (required)
├── hooks/ # Lifecycle hooks directory (required)
├── agents/ # Agent definitions directory (required)
└── commands/ # Custom commands directory (required)
Plugin Metadata Schema
The .claude-plugin/plugin.json file must contain these required fields:
{
"name": "plugin-name",
"version": "1.0.0",
"description": "Clear description of what the plugin does",
"author": {
"name": "Author Name",
"email": "[email protected]"
}
}
Naming Conventions
Plugin Names
- Use lowercase letters only
- Separate words with hyphens (kebab-case)
- Be descriptive but concise
- Avoid special characters
- Examples:
weather-forecast,code-formatter,task-manager
Directory Names
- Plugin directory name must match the
namefield inplugin.json - Example: If
nameis "example-calculator", directory must beplugins/example-calculator/
Validation Requirements
Before Any Changes
Always run the validation script before making changes:
./validate-plugins.sh
Plugin Validation Checks
The validation script checks for:
- Valid JSON syntax in
plugin.json - Presence of all required fields (
name,version,description,author) - Semantic versioning format (X.Y.Z)
- Directory name matching plugin name
- Presence of required subdirectories (
hooks/,agents/,commands/)
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.
- 8d ago First seen · 166 lines · 1,223 tokens per session scan A fe0871df4e97
awesome-claude-plugins copilot-instructions.md is an instructions file published in the GitHub repository GiladShoham/awesome-claude-plugins (51 stars, last pushed 11mo ago), licensed MIT. It adds 1,223 tokens to every session, about $0.0061 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.
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.