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 skills add ninihen1/power-automate-mcp-skills --skill flowstudio-power-automate-governancegit clone --depth 1 https://github.com/ninihen1/power-automate-mcp-skillsWrote 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/ninihen1/power-automate-mcp-skills/flowstudio-power-automate-governance)<a href="https://agentmods.dev/skills/ninihen1/power-automate-mcp-skills/flowstudio-power-automate-governance"><img src="https://agentmods.dev/badge/skills/ninihen1/power-automate-mcp-skills/flowstudio-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.
<a href="https://agentmods.dev/skills/ninihen1/power-automate-mcp-skills/flowstudio-power-automate-governance"><img src="https://agentmods.dev/badge/skills/ninihen1/power-automate-mcp-skills/flowstudio-power-automate-governance.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.00151 | $0.03341 |
| Opus 5 | $0.00076 | $0.01670 |
| Sonnet 5 | $0.00030 | $0.00668 |
| Haiku 4.5 | $0.00015 | $0.00334 |
Grade A, and why
flowstudio-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 13d 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
91% identical to flowstudio-power-automate-governance — 14 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 — 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 flowstudio-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 flowstudio-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— calltool_searchwithquery: "skill:governance"for the canonical bundle, orquery: "select:update_store_flow"for a single tool. This skill covers workflow patterns and field semantics — thingstool_searchcannot 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).
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.
- 13d ago First seen · 333 lines · 151 tokens per session scan A 847fc4c3df86
flowstudio-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 151 tokens to every session and 3,341 once invoked, about $0.0008 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 14 lines, and is treated as a copy.
Other skills, from other repositories
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
gws-tasks
Google Tasks: Manage task lists and tasks.
gws-workflow-standup-report
Google Workflow: Today's meetings + open tasks as a standup summary.
entity-compliance
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity…
integration-management
Post-closing M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initializes from whatever deal artifacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A cold-start.…
matter-workspace
Manage matter workspaces — new, list, switch, close, or detach (practice-level). File-management logic for keeping one client or engagement's context separate from every other. Use when working across multiple clients or matters, when the user says "new matter", "switch matter", "list matters", "close matter", or when…