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/magemaclean/azure-devops-mcp/agents-mdgit clone --depth 1 https://github.com/magemaclean/azure-devops-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/magemaclean/azure-devops-mcp/agents-md)<a href="https://agentmods.dev/instructions/magemaclean/azure-devops-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/magemaclean/azure-devops-mcp/agents-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.00898 | $0.00898 |
| Opus 5 | $0.00449 | $0.00449 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
azure-devops-mcp AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps MCP Server - Agent Instructions
Overview
This MCP server provides tools for interacting with Azure DevOps. It exposes a thin abstraction layer over Azure DevOps REST APIs, letting you handle complex reasoning while the tools handle data access.
Key Principles
- Simple & Focused: Each tool does one thing well. Use multiple tools for complex tasks.
- Always Check Available Tools: Before attempting any Azure DevOps operation, check if a relevant tool exists.
- Domain-Specific: Tools are organized by domains (core, work, work-items, repositories, pipelines, wiki, test-plans, search, advanced-security).
Available Domains
Tools are organized into these domains:
- core: Projects, teams, identities
- work: Iterations management
- work-items: Backlogs, work items, comments, linking
- repositories: Repos, pull requests, branches, commits
- pipelines: Builds, definitions, releases
- wiki: Wiki pages and content
- test-plans: Test plans, cases, results
- search: Search across code, wiki, work items
- advanced-security: Security alerts
Common Workflows
Starting Any Task
- First, list projects with
core_list_projectsto get the project name/ID - For team-specific operations, use
core_list_project_teamsto identify the team
Working with Work Items
- Use
wit_my_work_itemsto find user's work items - Use
wit_get_work_itemfor details (useexpand: "relations"to get child items) - Use
wit_update_work_itemfor updates - Link work items with
wit_work_items_linkor link to PRs withwit_link_work_item_to_pull_request
Repository Operations
- List repos:
repo_list_repos_by_project - List PRs:
repo_list_pull_requests_by_repoorrepo_list_pull_requests_by_project - Get PR details:
repo_get_pull_request_by_id(useincludeWorkItemRefs: truefor linked work items) - List PR threads/comments:
repo_list_pull_request_threadsandrepo_list_pull_request_thread_comments
Pipeline Operations
- List build definitions:
build_get_definitions - Get builds:
build_get_builds - Trigger builds:
build_run_build - Get build logs:
build_get_logorbuild_get_log_by_id
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 · 90 lines · 898 tokens per session scan A fb7e377a7217
azure-devops-mcp AGENTS.md is an instructions file published in the GitHub repository magemaclean/azure-devops-mcp (0 stars, last pushed 10mo ago), licensed MIT. It adds 898 tokens to every session, about $0.0045 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.