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/nickpolyder/np.copilot.config/copilot-instructionsgit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWhat 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.00938 | $0.00938 |
| Opus 5 | $0.00469 | $0.00469 |
| Sonnet 5 | $0.00188 | $0.00188 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
NP.CoPilot.Config 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — NP.CoPilot.Config
What This Repo Is
A global GitHub Copilot CLI configuration repository. It defines instructions, agents, skills, MCP server infrastructure, and installer scripts that apply across all workspaces via symlinks into ~/.copilot/.
This is not a typical code project — there are no build/test/lint pipelines. The deliverables are markdown definitions and PowerShell scripts.
Architecture
copilot-instructions.md → Root operating contract (symlinked to ~/.copilot/)
instructions/*.instructions.md → Canonical policies (coordination, workflow, lifecycle, delivery, style)
agents/*.md → Specialist agent definitions (17 agents)
skills/*/SKILL.md → Focused workflows (25 skills)
mcps/ → MCP integration support (remote Docker Compose: SearXNG only)
templates/ → Per-repo scaffolding templates (Generic, Angular, Blazor, Service Fabric) + repo-bootstrap/ (agent contract + docs memory tree)
mcp-config.json → MCP client config for SearXNG bridge + local Playwright
install.ps1 → Symlinks this repo into ~/.copilot/ (core install script)
install-project.ps1 → Scaffolds project-level templates into a target repo (-Template param)
mcps/deploy.ps1 → Deploys MCP Docker stack (Remote/Local/WSL modes)
Configuration Conflict Resolution (important for understanding scope)
Copilot combines applicable guidance from all of these sources:
- Global (
~/.copilot/) — this repo's content, always active - Project (
.github/instructions/*.instructions.md) — repository-specific guidance - Local (gitignored per-user files) — personal preferences
When combined guidance conflicts, use the most repository-specific instruction unless a higher-priority system or safety constraint prevents it.
Key Conventions
Agent Definitions (agents/*.md)
- Each file defines one specialist agent with a focused domain (architect, backend-dev, QA, etc.)
- Agents use tools (edit, search, commands) but never invoke orchestrator skills directly
- If an agent identifies work needing a skill, it recommends it to the user instead
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 · 81 lines · 938 tokens per session scan A ec6ce39c2f36
NP.CoPilot.Config copilot-instructions.md is an instructions file published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 7d ago), licensed MIT. It adds 938 tokens to every session, about $0.0047 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
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.
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).
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.