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 skills add jamesyang124/agent-skills --skill install-azure-devops-mcpgit clone --depth 1 https://github.com/jamesyang124/agent-skillsWrote 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/skills/jamesyang124/agent-skills/install-azure-devops-mcp)<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/install-azure-devops-mcp"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/install-azure-devops-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/install-azure-devops-mcp"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/install-azure-devops-mcp.svg" alt="Reviewed on agentmods" width="80" 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.00062 | $0.01009 |
| Opus 5 | $0.00031 | $0.00504 |
| Sonnet 5 | $0.00012 | $0.00202 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade B, and why
install-azure-devops-mcp scanned grade B with 1 finding 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 9d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
An env file is also written to `~/.env.mcp-azure-devops` (global, chmod 600). How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install Azure DevOps MCP
⚙️ Install this skill globally
Install once so it's available across all your projects.
Claude (global)
mkdir -p ~/.claude/skills/install-azure-devops-mcp
cp <agent-settings-repo>/.agent-settings/skills/tools/install-azure-devops-mcp/SKILL.md \
~/.claude/skills/install-azure-devops-mcp/SKILL.md
# Add to ~/.claude/CLAUDE.md:
# - **install-azure-devops-mcp** (`~/.claude/skills/install-azure-devops-mcp/SKILL.md`)
GitHub Copilot (global)
mkdir -p ~/.copilot/skills/install-azure-devops-mcp
cp <agent-settings-repo>/.agent-settings/skills/tools/install-azure-devops-mcp/SKILL.md \
~/.copilot/skills/install-azure-devops-mcp/SKILL.md
Adds Azure DevOps access to your agent: work items, repos, branches, PRs, pipelines, test plans, sprints, wikis. Repository: https://github.com/microsoft/azure-devops-mcp
Arguments
All optional — anything not passed is asked in Step 1.
| Token | Meaning |
|---|---|
claude / copilot |
which agent to configure |
| any other bare token | Azure DevOps organization name (e.g. mycompany) |
The PAT is never taken as an argument — it is collected in the terminal (Step 2).
Quick Start
Collect parameters, then run the bundled script. The PAT must be collected via terminal — never via a questions tool.
Step 1 — Collect parameters
Use vscode_askQuestions with:
- agent — which agent to configure
- options:
claude,copilot
- options:
- org — Azure DevOps organization name (e.g.
mycompany)
Step 2 — Run the installer
Find this skill's directory from the SKILL.md path, then run:
PROJECT_ROOT="<workspace-root>" \
bash .agent-settings/skills/tools/install-azure-devops-mcp/scripts/install.sh \
--agent <agent> \
--org <org>
- Set
PROJECT_ROOTto the user's current workspace folder - If
~/.env.mcp-azure-devopsalready exists, the script detects it and asks whether to reuse the stored PAT — no re-entry needed - PAT is always prompted interactively in the terminal (hidden input) when no existing file is found
- The script merges into any existing config file; it will not overwrite other servers
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 125 lines · 62 tokens per session scan B e2f8eabb31dc
install-azure-devops-mcp is a skill published in the GitHub repository jamesyang124/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,009 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.