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 skills/tiberriver256/mcp-server-azure-devops/azure-devops-rest-apinpx skills add Tiberriver256/mcp-server-azure-devops --skill azure-devops-rest-apigit clone --depth 1 https://github.com/Tiberriver256/mcp-server-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/skills/tiberriver256/mcp-server-azure-devops/azure-devops-rest-api)<a href="https://agentmods.dev/skills/tiberriver256/mcp-server-azure-devops/azure-devops-rest-api"><img src="https://agentmods.dev/badge/skills/tiberriver256/mcp-server-azure-devops/azure-devops-rest-api.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.00059 | $0.01442 |
| Opus 5 | $0.00030 | $0.00721 |
| Sonnet 5 | $0.00012 | $0.00288 |
| Haiku 4.5 | $0.00006 | $0.00144 |
Grade A, and why
azure-devops-rest-api 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- azure-devops-rest-api — 100% identical, 0 lines differ
- azure-devops-rest-api — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps REST API
Overview
This skill provides guidance for working with Azure DevOps REST APIs using the official OpenAPI specifications from the vsts-rest-api-specs repository. It helps with implementing new API integrations, understanding API capabilities, and referencing the correct request/response formats.
Key API Areas
Azure DevOps REST APIs are organized into the following main areas:
Core Services
- core - Projects, teams, processes, and organization-level operations
- git - Repositories, branches, pull requests, commits
- build - Build definitions, builds, and build resources
- pipelines - Pipeline definitions and runs
- release - Release definitions, deployments, and approvals
Work Item & Planning
- wit (Work Item Tracking) - Work items, queries, and work item types
- work - Boards, backlogs, sprints, and team configurations
- testPlan - Test plans, suites, and cases
- testResults - Test runs and results
Package & Artifact Management
- artifacts - Artifact feeds and packages
- artifactsPackageTypes - NuGet, npm, Maven, Python packages
Security & Governance
- graph - Users, groups, and memberships
- security - Access control lists and permissions
- policy - Branch policies and policy configurations
- audit - Audit logs and events
Extension & Integration
- extensionManagement - Extensions and marketplace
- serviceEndpoint - Service connections
- hooks - Service hooks and subscriptions
API Specification Structure
The vsts-rest-api-specs repository is organized by API area and version:
specification/
├── {api-area}/ (e.g., git, build, pipelines)
│ ├── 7.2/ Latest stable version
│ │ ├── {area}.json OpenAPI spec file
│ │ └── httpExamples/ Example requests/responses
│ ├── 7.1/
│ └── ...
Using the Specifications
- Identify the API area - Determine which service area (git, build, wit, etc.) contains the functionality needed
- Select the version - Use the latest version (7.2) unless targeting a specific Azure DevOps Server version
- Review the OpenAPI spec - The main
{area}.jsonfile contains all endpoints, schemas, and parameters - Check httpExamples - Real request/response examples for each endpoint
What ships with it
3 files 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.
- 5d ago First seen · 153 lines · 59 tokens per session scan A 98e66ff90660
azure-devops-rest-api is a skill published in the GitHub repository Tiberriver256/mcp-server-azure-devops (385 stars, last pushed 7d ago), licensed MIT. It adds 59 tokens to every session and 1,442 once invoked, about $0.0003 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 skills, from other repositories
update-change-log
To synchronize CHANGELOG.md with changes made last week (mon - sun).
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
post-mortem
Diagnose instruction defects and optionally submit Rosetta GitHub issue.
solr-extending
To build Solr plugins: SearchComponent, QParser, URP, DocTransformer.
solr-semantic-search
To build Solr phrase-tagging semantic search: concept tagging, taxonomy, graph paths.
help-flow
Help about Rosetta: explains capabilities and usage.