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/github/github-mcp-server/copilot-instructionsgit clone --depth 1 https://github.com/github/github-mcp-serverWhat 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.03217 | $0.03217 |
| Opus 5 | $0.01608 | $0.01608 |
| Sonnet 5 | $0.00643 | $0.00643 |
| Haiku 4.5 | $0.00322 | $0.00322 |
Grade A, and why
github-mcp-server 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- omnigit-mcp copilot-instructions.md — 97% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub MCP Server - Copilot Instructions
Project Overview
This is the GitHub MCP Server, a Model Context Protocol (MCP) server that connects AI tools to GitHub's platform. It enables AI agents to manage repositories, issues, pull requests, workflows, and more through natural language.
Key Details:
- Language: Go 1.24+ (~38k lines of code)
- Type: MCP server application with CLI interface
- Primary Package: github-mcp-server (stdio MCP server - this is the main focus)
- Secondary Package: mcpcurl (testing utility - don't break it, but not the priority)
- Framework: Uses modelcontextprotocol/go-sdk for MCP protocol, google/go-github for GitHub API
- Size: ~60MB repository, 70 Go files
- Library Usage: This repository is also used as a library by the remote server. Functions that could be called by other repositories should be exported (capitalized), even if not required internally. Preserve existing export patterns.
Code Quality Standards:
- Popular Open Source Repository - High bar for code quality and clarity
- Comprehension First - Code must be clear to a wide audience
- Clean Commits - Atomic, focused changes with clear messages
- Structure - Always maintain or improve, never degrade
- Code over Comments - Prefer self-documenting code; comment only when necessary
Critical Build & Validation Steps
Required Commands (Run Before Committing)
ALWAYS run these commands in this exact order before using report_progress or finishing work:
- Format Code:
script/lint(runsgofmt -s -w .thengolangci-lint) - Run Tests:
script/test(runsgo test -race ./...) - Update Documentation:
script/generate-docs(if you modified MCP tools/toolsets)
These commands are FAST: Lint ~1s, Tests ~1s (cached), Build ~1s
When Modifying MCP Tools/Endpoints
If you change any MCP tool definitions or schemas:
- Run tests with
UPDATE_TOOLSNAPS=true go test ./...to update toolsnaps - Commit the updated
.snapfiles inpkg/github/__toolsnaps__/ - Run
script/generate-docsto update README.md - Toolsnaps document API surface and ensure changes are intentional
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 · 291 lines · 3,217 tokens per session scan A 83a4bbbae137
github-mcp-server copilot-instructions.md is an instructions file published in the GitHub repository github/github-mcp-server (32,608 stars, last pushed 3d ago), licensed MIT. It adds 3,217 tokens to every session, about $0.0161 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
av CLAUDE.md
Instructions for aviator-co/av, covering claude.md, project overview, documentation sources, command structure philosophy and development workflow.
vscode-gitlens AGENTS.md
AGENTS.md instructions for gitkraken/vscode-gitlens, covering gitlens development guide, working style expectations, development environment, development commands and git & repository guidelines.
ghtkn AGENTS.md
Instructions for suzuki-shunsuke/ghtkn, a project described as: A CLI to create short-lived (8 hours) GitHub App User Access Token for secure local development.
vscode-gitlens CLAUDE.md
Claude Code instructions for gitkraken/vscode-gitlens, a project described as: Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via…
msaccess-vcs-addin AGENTS.md
AGENTS.md instructions for joyfullservice/msaccess-vcs-addin, covering project overview, repository structure, architecture overview, component diagram and key architectural patterns.
git-steer CLAUDE.md
Claude Code instructions for ry-ops/git-steer, covering git-steer project, project structure, development and aiana integration.