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/madskristensen/githubnode/copilot-instructionsgit clone --depth 1 https://github.com/madskristensen/GitHubNodeWhat 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.00378 | $0.00378 |
| Opus 5 | $0.00189 | $0.00189 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
GitHubNode 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.
What it actually says
Copilot Instructions
You must always strictly adhere to these instructions!
DEFINITION OF DONE - MANDATORY
Before writing any code, read this section. After writing code, execute every step below in order before responding.
Before marking any task as complete, you MUST perform ALL of the following steps in order:
- Read the
./.editorconfigfile at the repo root (if it exists) and verify all code changes adhere to its rules and the existing coding style conventions. - Run the build and verify it succeeds with no errors.
- Check the build output for warnings. Compare against pre-existing warnings and ensure your changes introduced zero new warnings. If new warnings are found, fix them before proceeding.
- If a unit test project exist, add new tests or update existing tests to cover your changes as appropriate. Ensure all tests pass locally.
- Run all unit tests and verify none are broken. If any tests fail due to your changes, fix them before proceeding.
Do NOT consider the task done until all five steps pass. Keep iterating until they do.
General Guidelines
- This is a Visual Studio extension project.
- It uses the latest version of C# that is supported on .NET Framework 4.8.
- Don't use emojis in .md files and elsewhere.
- Don't use the em-dash character (-), use single hyphens (-) surrounded by space characters instead.
Exception Handling
ALWAYS log caught exceptions using ex.LogAsync(). Never swallow an exception silently or use any other logging mechanism.
File Management
source.extension.cs and VSCommandTable.cs are generated files, but you can't generate them, so just edit them directly.
JSON Parsing
ALWAYS use System.Text.Json for JSON parsing. NEVER use Newtonsoft.Json or any other legacy serializer.
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 · 37 lines · 378 tokens per session scan A bb1b889bcf8a
GitHubNode copilot-instructions.md is an instructions file published in the GitHub repository madskristensen/GitHubNode (23 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 378 tokens to every session, about $0.0019 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.
buildNext
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
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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
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.
langchain 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.