git-integration-operations-cli

git-integration-operations-cli is a skill for Claude Code from microsoft/skills-for-fabric. It costs 92 tokens per session (9,981 once invoked), scanned A, original, MIT.

A skill for connecting Microsoft Fabric workspaces to Azure DevOps or GitHub and managing their Git synchronization. Git is a system for tracking code and configuration changes.

In plain words
What is it for?
Use it to connect or disconnect workspaces, commit Fabric changes, update from Git, check sync status, resolve conflicts, and automate synchronization with a service account.
Why use it?
It removes the need to manage workspace connection, commits, updates, conflicts, and synchronization status manually through separate requests.

Skill for Claude Code ✓ vendor

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the fabric-skills plugin — 25 skills shipped together

Good fit Use it to connect or disconnect workspaces, commit Fabric changes, update from Git, check sync status, resolve conflicts, and automate synchronization with a service account.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/skills-for-fabric/git-integration-operations-cli
About the project

Microsoft Fabric Skills is a collection of reusable instructions and MCP systems that help AI assistants work with Microsoft Fabric workloads, APIs, queries, and operations. It is intended for users of GitHub Copilot CLI and compatible coding tools; the catalogue entries are the skills, agents, instructions, MCP systems, plugins, and rules distributed by the project.

microsoft/skills-for-fabric · 1,321 stars · on GitHub

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.

Any agent
npx skills add microsoft/skills-for-fabric --skill git-integration-operations-cli
Clone the repo
git clone --depth 1 https://github.com/microsoft/skills-for-fabric

Made for: Claude Code.

Or install fabric-skills, the plugin that ships this one along with the rest of its 25 skills.

Wrote 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.

agentmods badge for git-integration-operations-cli

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/skills-for-fabric/git-integration-operations-cli/github.svg)](https://agentmods.dev/skills/microsoft/skills-for-fabric/git-integration-operations-cli)
Your own site
<a href="https://agentmods.dev/skills/microsoft/skills-for-fabric/git-integration-operations-cli"><img src="https://agentmods.dev/badge/skills/microsoft/skills-for-fabric/git-integration-operations-cli/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.

agentmods 80×15 button for git-integration-operations-cli

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/skills-for-fabric/git-integration-operations-cli"><img src="https://agentmods.dev/badge/skills/microsoft/skills-for-fabric/git-integration-operations-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,981 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 7 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 236
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • medium Data Exfiltration · line 143
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 614
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 619
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 166
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 215
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 214
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
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.1 $0.00092 $0.09981
Opus 5.5 $0.00037 $0.03992
Sonnet 5.5 $0.00018 $0.01996
Haiku 4.5 $0.00009 $0.00998

Measured yesterday against content hash 4b010037ad92, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-integration-operations-cli scanned grade A 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| Target `directoryName` exists on the branch | GitHub: `curl -fsS -H "Authorization: Bearer $PAT" "https://api.github.com/repos/$OWNER/$REPO/contents/$DIR?ref=$BRANCH"` — ADO: Items API on the repo | The API (unlike the
plugins/fabric-skills/skills/git-integration-operations-cli/SKILL.md · 721 lines

How it starts

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

Telemetry — MANDATORY. Every api.fabric.microsoft.com call must carry x-ms-fabric-skill: git-integration-operations-cli (az rest: --headers "x-ms-fabric-skill=git-integration-operations-cli"), including every LRO poll, fabric_lro and retry. Snippets omit it — add it anyway.

CRITICAL NOTES

  1. To find a workspace ID from its name: list all workspaces, then filter by displayName with JMESPath. To find an item ID: list items of that type in the workspace, then filter by displayName.
  2. All Git operations are control plane calls against https://api.fabric.microsoft.com. Run fab auth login once and fab api sets the base URL and Fabric token audience automatically. With the az rest fallback you must pass the matching --resource yourself, or you get a 401.
  3. commitToGit, updateFromGit, and even git/status can return HTTP 202 (long-running operation), not just a synchronous body. On 202, poll the operation: with fab, read x-ms-operation-id from --show_headers and poll fab api operations/{id} until status is Succeeded; with the az rest fallback, poll the Location / x-ms-operation-id header (see COMMON-CORE long-running operation polling). When a 202 came from git/status itself, read its body from operations/{id}/result (the git_status helper does this); calling git/status again can just return another 202. After a commitToGit / updateFromGit operation succeeds, read status with git_status to confirm workspaceHead == remoteCommitHash, and do not act on its changes until the heads match. (Learn: rest/api/fabric/core/git and fabric/cicd/git-integration/git-automation.)
  4. updateFromGit requires the workspace's current workspaceHead; a stale value returns 400 WorkspaceHeadMismatch. Always read git/status first.
  5. Prerequisites for every Git operation: the workspace must be assigned to a capacity (an unassigned workspace fails with WorkspaceHasNoCapacityAssigned), and the caller (user or service principal) must hold the right workspace role: connect and disconnect require Admin; commit and update require at least Contributor with write permission on all items; branch switching requires Admin (or Contributor when the workspace opt-in setting Allow users with at least Contributor role to change Git branch is on). Only one Git operation may run against a workspace at a time.
  6. Tenant admin switches gate Git integration and are a common cause of an unexplained failure. The GitHub sync switch is off by default (enable it before any GitHub connect); Azure DevOps sync is on by default. Cross-region workspace-to-Azure-repo needs the cross-geo export switch (GitHub does not enforce it). See references/git-integration-concepts.md § Tenant admin prerequisites.

Git Integration Operations — CLI Skill

Automate the Fabric Git integration lifecycle (connect, commit, update, status, disconnect) from CLI environments. Whether cross-workspace item references rebind after promotion is a separate concern, determined by the item definition format (logical vs object IDs) rather than the Git lifecycle itself.

Read the full file on GitHub · 721 lines

Files

What ships with it

2 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.

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. yesterday Changed · +97 lines 4b010037ad92
  2. 2mo ago First seen · 624 lines · 92 tokens per session scan A bd67a6cb16a8

Subscribe to this mod's changes

git-integration-operations-cli is a skill published in the GitHub repository microsoft/skills-for-fabric (1,321 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 9,981 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

git-integration-operations-cli compared with skills from other repositories

git-integration-operations-cli next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
git-integration-operations-climicrosoft/skills-for-fabricSkill1.3kyesterdayMITA92Claude Code
merge-batchdiegosouzapw/OmniRouteSkill83k6d agoMITA46Claude Code
prowler-commitprowler-cloud/prowlerSkill15kyesterdayApache-2.0A44Claude Code, Codex
gh-auth-isolationgithub/gh-awSkill5.6kyesterdayMITA20Claude Code, Codex
github-skillzeenie-ai/OpenCompanySkill1.1kyesterdayMITA51Claude Code
comet-githubrpamis/cometSkill3.3kyesterdayMITA72Claude Code, Codex
release-helperSahir619/fable-methodSkill2.3k1mo agoMITA43Claude Code