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/uhvogala/azure-devops-mcp-vscode/agents-mdgit clone --depth 1 https://github.com/uhvogala/azure-devops-mcp-vscodeWrote 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/uhvogala/azure-devops-mcp-vscode/agents-md)<a href="https://agentmods.dev/instructions/uhvogala/azure-devops-mcp-vscode/agents-md"><img src="https://agentmods.dev/badge/instructions/uhvogala/azure-devops-mcp-vscode/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.1 | $0.00278 | $0.00278 |
| Opus 5 | $0.00139 | $0.00139 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
azure-devops-mcp-vscode 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 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.
What it actually says
Agent Guidance
VS Code reuses the existing Microsoft session for Azure DevOps MCP tools. Do not run Azure DevOps PRs (MCP): Sign In to Azure DevOps routinely; ask the user to complete sign-in only when an operation reports missing or expired authentication.
Keep VS Code's built-in Git extension enabled. This extension uses its repository API for workspace discovery, checkout, and local pull request refreshes.
When the Azure DevOps organization, project, or repository is unknown, call get_workspace_repositories once. Prefer its activeRepository; otherwise use the returned workspace repository list rather than searching files or manually parsing Git remotes.
When a user asks to show, open, view, or review a specific pull request, call get_pull_request directly. It renders the interactive review card. Use list_pull_requests only when the pull request ID is unknown.
Use create_pull_request to prepare a local editable draft. It does not create a remote pull request. Present the draft for the user to edit, ask whether they want any text changes, and wait for explicit confirmation before using submit_pull_request, which creates the remote PR and requires confirm: true.
Run npm test before completing extension changes. Package with npx vsce package after a version bump when a local install or release artifact is needed.
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 · 14 lines · 278 tokens per session scan A f7a323c3e323
azure-devops-mcp-vscode AGENTS.md is an instructions file published in the GitHub repository uhvogala/azure-devops-mcp-vscode (0 stars, last pushed 4d ago), licensed MIT. It adds 278 tokens to every session, about $0.0014 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
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.
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).
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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.