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/wangkanai/devops-mcp/claude-mdgit clone --depth 1 https://github.com/wangkanai/devops-mcpWhat 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.04203 | $0.04203 |
| Opus 5 | $0.02101 | $0.02101 |
| Sonnet 5 | $0.00841 | $0.00841 |
| Haiku 4.5 | $0.00420 | $0.00420 |
Grade A, and why
devops-mcp 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 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.
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 — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - DevOps MCP for Claude Code Integration
Comprehensive context for Claude Code to work effectively with the Azure DevOps MCP server for seamless project management and development workflows.
📋 Project Overview
devops-mcp - Azure DevOps MCP Server for Claude
Technology: Node.js, TypeScript, MCP Protocol
Purpose: Dynamic Azure DevOps integration with intelligent directory-based authentication switching
Status: ✅ PRODUCTION READY - Active deployment with >95% test coverage
GitHub: https://github.com/wangkanai/devops-mcp
NPM Package: @wangkanai/devops-mcp
Features: Local .azure-devops.json configuration, secure PAT tokens, comprehensive testing, full Azure DevOps API integration
🚀 Quick Start for Claude Users
Immediate Setup (2 minutes)
# 1. Install via Claude Code (Recommended)
claude mcp add devops-mcp -- -y @wangkanai/devops-mcp
# 2. Create configuration in your project directory
cat > .azure-devops.json << EOF
{
"organizationUrl": "https://dev.azure.com/your-org",
"project": "YourProject",
"pat": "your-pat-token-here",
"description": "Azure DevOps configuration for this repository"
}
EOF
# 3. Secure your configuration
echo ".azure-devops.json" >> .gitignore
# 4. Verify installation
mcp__devops-mcp__get-current-context
Claude Desktop Users
Add to your MCP settings file:
{
"mcpServers": {
"devops-mcp": {
"command": "npx",
"args": ["-y", "@wangkanai/devops-mcp"]
}
}
}
Settings Location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
🎯 Core Capabilities for Claude
Smart Context Switching
Claude automatically detects project context based on your current directory:
- RiverSync projects: Auto-switches to
https://dev.azure.com/riversync - Mula projects: Auto-switches to
https://dev.azure.com/mula-x - Any project: Uses local
.azure-devops.jsonconfiguration
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 · 484 lines · 4,203 tokens per session scan A 27bb03de6f36
devops-mcp CLAUDE.md is an instructions file published in the GitHub repository wangkanai/devops-mcp (12 stars, last pushed 5mo ago), licensed MIT. It adds 4,203 tokens to every session, about $0.0210 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.