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/itstanner5216/multi-mcp/copilot-instructionsgit clone --depth 1 https://github.com/itstanner5216/multi-mcpWrote 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/itstanner5216/multi-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/itstanner5216/multi-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/itstanner5216/multi-mcp/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 | $0.00981 | $0.00981 |
| Opus 5 | $0.00491 | $0.00491 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
multi-mcp copilot-instructions.md scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`requests.get()`, `time.sleep()`) made outside of an executor — suggest `anyio`/`asyncio` How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Code Review Instructions
These instructions define how GitHub Copilot should review pull requests in this repository.
This is a production-grade Python MCP (Model Context Protocol) proxy server built on asyncio,
anyio, Starlette, Pydantic, and loguru. Apply the following standards on every review.
Architecture & Design
- This codebase uses an async-first architecture. Flag any blocking I/O calls (e.g.,
open(),requests.get(),time.sleep()) made outside of an executor — suggestanyio/asyncioasync equivalents instead. - All configuration must flow through Pydantic models (
pydantic-settings). Flag any rawos.environoros.getenvcalls that bypass the settings layer. - The proxy pattern (aggregating multiple MCP backends into one endpoint) is core to this project. Flag any code that tightly couples business logic to a specific backend transport (stdio vs SSE) — these should be abstracted.
- Prefer dependency injection over global state. Flag module-level mutable globals.
Security
- Flag any place where the
--api-keyvalue could be logged, printed, or exposed in tracebacks. API keys must never appear in log output at any level. - Flag any use of
subprocessorshell=Truewithout explicit input sanitisation. - Flag any dynamic
eval(),exec(), or__import__()usage. - Flag any file path construction that uses raw string concatenation instead of
pathlib.Path. - Ensure all external HTTP calls use
httpx(the project standard) — flag use ofrequestsin new code sincerequestsis synchronous and not appropriate for this async codebase.
Code Quality
- All public functions and classes must have docstrings. Flag missing docstrings on anything
that is not a private helper (
_prefix). - Type annotations are required on all function signatures. Flag unannotated parameters or return types.
- Pydantic v2 patterns must be used throughout. Flag any Pydantic v1 patterns such as
.dict(),.parse_obj(),validatordecorators — suggest v2 equivalents (.model_dump(),.model_validate(),@field_validator). - Flag bare
except:orexcept Exception:clauses without logging or re-raising — silent swallowing of exceptions is not acceptable in a proxy server. - Flag any
TODO,FIXME, orHACKcomments introduced in the PR diff.
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.
- 3d ago First seen · 83 lines · 981 tokens per session scan A 33a1d42092b6
multi-mcp copilot-instructions.md is an instructions file published in the GitHub repository itstanner5216/multi-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 981 tokens to every session, about $0.0049 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.