What is power-automate-governance?

A governance skill for Power Automate flows and Power Apps, Microsoft tools for building business automations and applications. It uses FlowStudio's cached store to classify flows, find unused resources, audit connectors, apply compliance metadata, manage notifications, and calculate governance scores.

Use it to classify and tag flows, detect orphaned resources, review connector use, enforce governance standards, manage notification rules, and calculate governance scores.

It provides centralized oversight of automation resources without relying on Dataverse, the CoE Starter Kit, or the Power Automate portal.

power-automate-governance — Skill for Claude Code by ninihen1

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 ninihen1/power-automate-mcp-skills --skill power-automate-governance

Clone the repo

git clone --depth 1 https://github.com/ninihen1/power-automate-mcp-skills

Made for: Claude Code.

Or install flowstudio-power-automate, the plugin that ships this one along with the rest of its 10 skills, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ninihen1/power-automate-mcp-skills/power-automate-governance/github.svg)](https://agentmods.dev/skills/ninihen1/power-automate-mcp-skills/power-automate-governance)

Your own site

<a href="https://agentmods.dev/skills/ninihen1/power-automate-mcp-skills/power-automate-governance"><img src="https://agentmods.dev/badge/skills/ninihen1/power-automate-mcp-skills/power-automate-governance/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ninihen1/power-automate-mcp-skills/power-automate-governance"><img src="https://agentmods.dev/badge/skills/ninihen1/power-automate-mcp-skills/power-automate-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 149 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,327 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 91% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00149	$0.03327
Opus 5	$0.00075	$0.01664
Sonnet 5	$0.00030	$0.00665
Haiku 4.5	$0.00015	$0.00333

Measured 12d ago against content hash 14e544c59392, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

power-automate-governance 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 12d 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.

Origin

This is a copy

91% identical to flowstudio-power-automate-governance — 28 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.

skills/power-automate-governance/SKILL.md · 333 lines

How it starts

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

Power Automate Governance with FlowStudio MCP

Classify, tag, and govern Power Automate flows at scale through the FlowStudio MCP cached store — without Dataverse, without the CoE Starter Kit, and without the Power Automate portal.

This skill uses the same store_* tool family as power-automate-monitoring, but with a different intent: governance writes metadata (update_store_flow) and reads for audit and classification outcomes. Monitoring reads the same tools for operational health outcomes. Don't try to memorize which skill "owns" which tool — pick by what the user is doing. For health checks and failure-rate dashboards, load power-automate-monitoring instead.

⚠️ Pro+ subscription required. This skill calls store_* tools that only work for FlowStudio for Teams or MCP Pro+ subscribers.

If the user does not have Pro+ access: the first store_* tool call will return a 403/404 error. When that happens:

STOP calling store tools

Tell the user governance features require a Pro+ subscription

Link them to https://mcp.flowstudio.app/pricing

Discovery: load tool schemas via the meta-tools rather than tools/list — call tool_search with query: "skill:governance" for the canonical bundle, or query: "select:update_store_flow" for a single tool. This skill covers workflow patterns and field semantics — things tool_search cannot tell you. If this document disagrees with a real API response, the API wins.

Critical: How to Extract Flow IDs

list_store_flows returns id in format <environmentId>.<flowId>. You must split on the first . to get environmentName and flowName for all other tools:

id = "Default-<envGuid>.<flowGuid>"
environmentName = "Default-<envGuid>"    (everything before first ".")
flowName = "<flowGuid>"                  (everything after first ".")

Also: skip entries that have no displayName or have state=Deleted — these are sparse records or flows that no longer exist in Power Automate. If a deleted flow has monitor=true, suggest disabling monitoring (update_store_flow with monitor=false) to free up a monitoring slot (standard plan includes 20).

Read the full file on GitHub · 333 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.

12d ago First seen · 333 lines · 149 tokens per session scan A 14e544c59392

Subscribe to this mod's changes

power-automate-governance is a skill published in the GitHub repository ninihen1/power-automate-mcp-skills (32 stars, last pushed 8d ago), licensed MIT. It adds 149 tokens to every session and 3,327 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to flowstudio-power-automate-governance, differing in 28 lines, and is treated as a copy.

DevOps and cloud Security gemini-cli-extension

power-automate-governance

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Power Automate Governance with FlowStudio MCP

Critical: How to Extract Flow IDs

What this file has done since we first saw it

Other skills, from other repositories

gws-gmail-send

gws-gmail

gws-shared

gws-sheets

gws-modelarmor-create-template

gws-modelarmor