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/vortiago/mcp-azure-devops/claude-mdgit clone --depth 1 https://github.com/Vortiago/mcp-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/vortiago/mcp-azure-devops/claude-md)<a href="https://agentmods.dev/instructions/vortiago/mcp-azure-devops/claude-md"><img src="https://agentmods.dev/badge/instructions/vortiago/mcp-azure-devops/claude-md.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.01878 | $0.01878 |
| Opus 5 | $0.00939 | $0.00939 |
| Sonnet 5 | $0.00376 | $0.00376 |
| Haiku 4.5 | $0.00188 | $0.00188 |
Grade A, and why
mcp-azure-devops CLAUDE.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 5d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Azure DevOps Server Guide
This guide helps AI assistants implement and modify the MCP Azure DevOps server codebase effectively.
1. Purpose & Overview
This MCP server enables AI assistants to interact with Azure DevOps by:
- Connecting to Azure DevOps services via REST API and Python SDK
- Exposing Azure DevOps data (work items, repositories, pipelines, PRs)
- Providing tools to create and modify Azure DevOps objects
- Including prompts for common workflows
- Using PAT authentication for secure interactions
2. Project Structure
mcp-azure-devops/
├── docs/ # API documentation
├── src/ # Source code
│ └── mcp_azure_devops/ # Main package
│ ├── features/ # Feature modules
│ │ ├── projects/ # Project management features
│ │ ├── teams/ # Team management features
│ │ └── work_items/ # Work item management features
│ │ ├── tools/ # Work item operation tools
│ │ ├── common.py # Common utilities for work items
│ │ └── formatting.py # Formatting helpers
│ ├── utils/ # Shared utilities
│ ├── __init__.py # Package initialization
│ └── server.py # Main MCP server
├── tests/ # Test suite
├── .env # Environment variables (not in repo)
├── CLAUDE.md # AI assistant guide
├── LICENSE # MIT License
├── pyproject.toml # Project configuration
├── README.md # Project documentation
└── uv.lock # Package dependency locks
3. Core Concepts
Azure DevOps & MCP Integration
This project bridges two systems:
-
Azure DevOps Objects:
- Work items (bugs, tasks, user stories, epics)
- Repositories and branches
- Pull requests and code reviews
- Pipelines (build and release)
- Projects and teams
-
MCP Components:
- Tools: Action performers that modify data (like POST/PUT/DELETE endpoints)
- Prompts: Templates for guiding interactions
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.
- 5d ago First seen · 281 lines · 1,878 tokens per session scan A 1183030cd815
mcp-azure-devops CLAUDE.md is an instructions file published in the GitHub repository Vortiago/mcp-azure-devops (79 stars, last pushed 10mo ago), licensed MIT. It adds 1,878 tokens to every session, about $0.0094 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
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.