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/paulvineethp/mcp-server-azure-devops/copilot-instructionsgit clone --depth 1 https://github.com/PaulVineethP/mcp-server-azure-devopsWrote 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/paulvineethp/mcp-server-azure-devops/copilot-instructions)<a href="https://agentmods.dev/instructions/paulvineethp/mcp-server-azure-devops/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/paulvineethp/mcp-server-azure-devops/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.02384 | $0.02384 |
| Opus 5 | $0.01192 | $0.01192 |
| Sonnet 5 | $0.00477 | $0.00477 |
| Haiku 4.5 | $0.00238 | $0.00238 |
Grade A, and why
mcp-server-azure-devops 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 4d 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.
This is a copy
100% identical to mcp-server-azure-devops copilot-instructions.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps MCP Server - Development Instructions
Always reference these instructions first and fallback to search or bash commands only when you encounter unexpected information that does not match the info here.
Prerequisites
You need to have Node.js and npm installed. Node 20 (LTS) or later is recommended for development.
Building and Running
1. Install Dependencies
npm install # Takes ~25 seconds. NEVER CANCEL. Set timeout to 60+ seconds.
2. Build the Server
npm run build # Takes ~5 seconds. Compiles TypeScript to `dist/` directory.
3. Run Tests
# Unit tests (no Azure DevOps credentials required)
npm run test:unit # Takes ~19 seconds. NEVER CANCEL. Set timeout to 60+ seconds.
# Integration tests (requires Azure DevOps credentials)
npm run test:int # Takes ~18 seconds. NEVER CANCEL. Set timeout to 60+ seconds.
# E2E tests (requires Azure DevOps credentials)
npm run test:e2e # Takes ~6 seconds. NEVER CANCEL. Set timeout to 30+ seconds.
# All tests
npm test # Takes ~45 seconds total. NEVER CANCEL. Set timeout to 90+ seconds.
4. Code Quality
npm run lint # Takes ~3 seconds. Runs ESLint for code quality.
npm run lint:fix # Auto-fix linting issues.
npm run format # Takes ~3 seconds. Runs Prettier for code formatting.
5. Run the Server
# IMPORTANT: Always configure environment first using `.env` file (copy from `.env.example`)
npm run dev # Development mode with auto-restart using ts-node-dev
npm run start # Production mode - runs compiled version from `dist/index.js`
npm run inspector # Debug mode with MCP Inspector tool
Environment Setup
Copy .env.example to .env and configure Azure DevOps credentials:
cp .env.example .env
# Edit .env with your Azure DevOps credentials
Required environment variables:
AZURE_DEVOPS_ORG_URL=https://dev.azure.com/your-organization
AZURE_DEVOPS_AUTH_METHOD=pat # Options: pat, azure-identity, azure-cli
AZURE_DEVOPS_PAT=your-personal-access-token # For PAT auth
AZURE_DEVOPS_DEFAULT_PROJECT=your-project-name # Optional
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.
- 4d ago First seen · 257 lines · 2,384 tokens per session scan A c2ecfb098a30
mcp-server-azure-devops copilot-instructions.md is an instructions file published in the GitHub repository PaulVineethP/mcp-server-azure-devops (0 stars, last pushed 2mo ago), licensed MIT. It adds 2,384 tokens to every session, about $0.0119 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mcp-server-azure-devops copilot-instructions.md, differing in 0 lines, and is treated as a copy.
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.