devops.fabric-mcp-integration

devops.fabric-mcp-integration is a skill for Claude Code, Codex from microsoft/DataFactory.MCP. It costs 37 tokens per session (1,099 once invoked), scanned A, original, MIT.

A set of instructions for DevOps and continuous integration work with Microsoft's Fabric.Mcp.Server, a system used to build and test software automatically.

In plain words
What is it for?
Use it when publishing packages, checking feed availability, troubleshooting package restores, or diagnosing CI failures in the named Microsoft repositories.
Why use it?
It explains why builds may fail to find newly published NuGet packages when the configured Azure DevOps feed has not cached them yet.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/microsoft/datafactory.mcp/devops.fabric-mcp-integration
Any agent
npx skills add microsoft/DataFactory.MCP --skill devops.fabric-mcp-integration
Clone the repo
git clone --depth 1 https://github.com/microsoft/DataFactory.MCP

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,099 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.01099
Opus 5 $0.00018 $0.00549
Sonnet 5 $0.00007 $0.00220
Haiku 4.5 $0.00004 $0.00110

Measured 3d ago against content hash 519bb4ddd2ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devops.fabric-mcp-integration 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.

.github/skills/devops.fabric-mcp-integration/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DevOps Integration with Fabric.Mcp.Server

Overview

The microsoft/mcp repo consumes Microsoft.DataFactory.MCP.Core as a NuGet package in Fabric.Mcp.Tools.DataFactory. CI builds use a DevOps feed with upstream caching from nuget.org — packages are not immediately available after publishing.

Feed Configuration

The Fabric.Mcp.Server NuGet.config uses a single feed:

<packageSources>
    <clear />
    <add key="azure-sdk-for-net"
         value="https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-net/nuget/v3/index.json" />
</packageSources>

How Upstream Caching Works

  1. A new version is published to nuget.org
  2. It is NOT immediately available on the DevOps feed
  3. A Collaborator runs dotnet restore against the DevOps feed
  4. The feed fetches and caches the package from nuget.org
  5. Subsequent Fabric.Mcp.Server CI builds can then resolve it

Important: The nuget list search index can lag behind actual availability. If dotnet restore succeeds, the package IS available for CI even if nuget list doesn't show it yet.

After Publishing a New Version

Step 1: Verify on nuget.org

nuget list Microsoft.DataFactory.MCP.Core \
  -Source "https://api.nuget.org/v3/index.json" \
  -PreRelease -AllVersions

Step 2: Trigger the DevOps feed to cache it

Run from the microsoft/mcp repo root:

dotnet restore tools/Fabric.Mcp.Tools.DataFactory/src/Fabric.Mcp.Tools.DataFactory.csproj \
  --source "https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-net/nuget/v3/index.json"

If restore succeeds, the package is cached and Fabric.Mcp.Server CI will find it.

Step 3: Verify (optional)

nuget list Microsoft.DataFactory.MCP.Core \
  -Source "https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-net/nuget/v3/index.json" \
  -PreRelease -AllVersions

Read the full file on GitHub · 128 lines

Changes

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.

  1. 3d ago First seen · 128 lines · 37 tokens per session scan A 519bb4ddd2ac

Subscribe to this mod's changes

devops.fabric-mcp-integration is a skill published in the GitHub repository microsoft/DataFactory.MCP (42 stars, last pushed 21d ago), licensed MIT. It adds 37 tokens to every session and 1,099 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

dsh-web-pre-push-checks

Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.

zhu1090093659/dsh-web · 45 tokens

babysit

Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…

kirodotdev/KiroCrew · 137 tokens

azsdk-common-pipeline-analysis

Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…

Azure/azure-sdk-for-net · 192 tokens

managing-github-actions-secrets

Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.

PostHog/posthog-foss · 67 tokens

ship-safe-ci

Run Ship Safe in CI mode — compact output, exit codes, SARIF generation. Use when the user wants to set up CI/CD security gates or test their pipeline configuration.

asamassekou10/ship-safe · 39 tokens

upgrading-golang

Upgrades Go version across the entire Chainloop codebase including source files, Docker images, CI/CD workflows, and documentation. Use when the user mentions upgrading Go, golang version, or updating Go compiler version.

chainloop-dev/chainloop · 48 tokens