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 boshi-xixixi/TraeSkill --skill flowstudio-power-automate-governancegit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/flowstudio-power-automate-governance)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/flowstudio-power-automate-governance"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/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/boshi-xixixi/traeskill/flowstudio-power-automate-governance"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/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 7d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- flowstudio-power-automate-governance — 91% identical, 14 lines differ
- power-automate-governance — 91% identical, 28 lines differ
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.
- 7d ago First seen · 333 lines · 151 tokens per session scan A e0d2b62d51ca
flowstudio-power-automate-governance is a skill published in the GitHub repository boshi-xixixi/TraeSkill (263 stars, last pushed 4mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
to-issues
A planning aid that breaks a PRD or technical specification into small implementation issues, each covering a complete, demonstrable piece of work.
fable-orchestrate
Use when the user wants a task decomposed and driven by a Fable 5.1 orchestrator delegating implementation to Sonnet 5 workers. Fable decomposes into self-contained specs, dispatches Sonnet workers (Agents for 1–2 pieces, a Workflow for fan-out), reviews each result, merges into one branch, and takes a binding verdict…
fable-validate-loop
Use when the user asks to validate a GitHub issue with Fable 5.1 and then autonomously drive it to a reviewed PR in one shot — "fable-validate-loop", "fable validate and work on.
fable-validate-fableplan-loop
Use when the user asks to validate a GitHub issue with Fable 5.1, always plan it with Fable 5.1, and autonomously drive it to a reviewed PR in one shot — "fable-validate-fableplan-loop", "fable validate, fable plan, and work on.
milestoneplan
Use when the user wants a milestone's execution plan shown as a table — "milestoneplan v1", "/milestoneplan", "show the plan for v1". Read-only - reads every issue in the milestone and renders one table of issue number, description, complexity, dependencies, validate/build model and effort, fableplan, plan effort, and…
new-issue
Use when the user says "new issue", "create an issue", "file an issue", "/new-issue", or asks to turn a bug, idea, or discussion into a GitHub issue. Takes an optional description of what the issue should cover; with no input, derives the issue from what was discussed in the current conversation. Verifies claims…