Borrowing it
Nothing to install: this file belongs to PaulVineethP/mcp-server-azure-devops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PaulVineethP/mcp-server-azure-devops/main/.github/skills/azure-devops-rest-api/SKILL.mdgit clone --depth 1 https://github.com/PaulVineethP/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/paulvineethp/mcp-server-azure-devops/azure-devops-rest-api)<a href="https://agentmods.dev/skills/paulvineethp/mcp-server-azure-devops/azure-devops-rest-api"><img src="https://agentmods.dev/badge/skills/paulvineethp/mcp-server-azure-devops/azure-devops-rest-api/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/paulvineethp/mcp-server-azure-devops/azure-devops-rest-api"><img src="https://agentmods.dev/badge/skills/paulvineethp/mcp-server-azure-devops/azure-devops-rest-api.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.00059 | $0.01442 |
| Opus 5.5 | $0.00024 | $0.00577 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to azure-devops-rest-api — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 153 lines · 59 tokens per session scan A 98e66ff90660
azure-devops-rest-api is a skill published in the GitHub repository PaulVineethP/mcp-server-azure-devops (1 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 1,442 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to azure-devops-rest-api, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
api-design
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…