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/vhcg77/github-copilot-instructions/copilot-instructionsgit clone --depth 1 https://github.com/vhcg77/github-copilot-instructionsWhat 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.04815 | $0.04815 |
| Opus 5 | $0.02407 | $0.02407 |
| Sonnet 5 | $0.00963 | $0.00963 |
| Haiku 4.5 | $0.00481 | $0.00481 |
Grade A, and why
github-copilot-instructions 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 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 — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot General Instructions
About Me
I am a Senior Data Scientist. My main focus is on developing robust, scalable, and maintainable data science solutions. I work with Python in Visual Studio Code. My expertise includes data cleaning, exploratory data analysis (EDA), statistical modeling, machine learning, and MLOps.
About This Project
This repository contains utilities for Gasco - a comprehensive data application built on Google Cloud Platform for inventory analysis and resource management. The project encompasses everything from data engineering and MLOps to frontend development.
Project Structure
/data: Raw and processed datasets, configuration files/notebooks: Jupyter notebooks for exploration (e.g.,analisis_exploratorio_inventario.ipynb)/src: Modular Python source code (data processing, utilities, documentation tools)/tests: Unit and integration tests using pytest/terraform: Infrastructure as Code for GCP deployment/.vscode: VS Code workspace configuration with GitHub Copilot integration/.github/instructions: Hierarchical instruction system for GitHub Copilot
Current Dataset Context
- Primary focus: Inventory analysis (
inventario_recursos_gasco_2025_06_25.csv) - Asset management: JSON data for assets tracking (
assets_gasco_2025_06_25.json) - Analysis outputs: Query analysis logs and structured reports
- Business domain: Resource inventory, asset tracking, operational analytics
Tech Stack
This project utilizes a modern, cloud-native tech stack centered around Python and Google Cloud Platform (GCP).
The specific technologies and libraries for a given task depend on the role being performed. You MUST refer to the detailed tech stack defined in the relevant file within the .github/instructions/roles/ directory (e.g., data-scientist.md, data-engineer.md, mlops-engineer.md, frontend-developer.md, cloud-architect.md, qa-engineer.md, visualization-engineer.md, business-analyst.md, project-manager.md).
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 · 496 lines · 4,815 tokens per session scan A 8e748f5d270b
github-copilot-instructions copilot-instructions.md is an instructions file published in the GitHub repository vhcg77/github-copilot-instructions (2 stars, last pushed 1y ago), licensed MIT. It adds 4,815 tokens to every session, about $0.0241 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
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).
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.
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.
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).
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.