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-monitoringgit 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-monitoring)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/flowstudio-power-automate-monitoring"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/flowstudio-power-automate-monitoring/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-monitoring"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/flowstudio-power-automate-monitoring.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.00105 | $0.03481 |
| Opus 5 | $0.00053 | $0.01741 |
| Sonnet 5 | $0.00021 | $0.00696 |
| Haiku 4.5 | $0.00011 | $0.00348 |
Grade A, and why
flowstudio-power-automate-monitoring 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 9d 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-monitoring — 100% identical, 4 lines differ
- power-automate-monitoring — 94% identical, 20 lines differ
How it starts
The opening of the file, as written. The whole thing — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power Automate Monitoring with FlowStudio MCP
Monitor flow health, track failure rates, and inventory tenant assets through the FlowStudio MCP cached store — fast reads, no PA API rate limits, and enriched with governance metadata and remediation hints.
⚠️ 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 this feature requires a Pro+ subscription
- Link them to https://mcp.flowstudio.app/pricing
- If their question can be answered with live tools (e.g. "list flows in one environment"), offer to use the
flowstudio-power-automate-mcpskill insteadDiscovery: load tool schemas via
tool_searchrather thantools/list— call withquery: "select:list_store_flows,get_store_flow_summary"for the common monitoring tools, or load the full set withquery: "skill:governance"(the server's governance bundle covers most monitoring reads too — this skill andflowstudio-power-automate-governanceshare the underlying tool family). This skill covers response shapes, behavioral notes, and workflow patterns — thingstool_searchcannot tell you. If this document disagrees with a real API response, the API wins.
How Monitoring Works
Flow Studio scans the Power Automate API daily for each subscriber and caches the results. There are two levels:
- All flows get metadata scanned: definition, connections, owners, trigger
type, and aggregate run statistics (
runPeriodTotal,runPeriodFailRate, etc.). Environments, apps, connections, and makers are also scanned. - Monitored flows (
monitor: true) additionally get per-run detail: individual run records with status, duration, failed action names, and remediation hints. This is what populatesget_store_flow_runsandget_store_flow_summary.
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.
- 9d ago First seen · 374 lines · 105 tokens per session scan A a2e7e9c8d4f9
flowstudio-power-automate-monitoring is a skill published in the GitHub repository boshi-xixixi/TraeSkill (263 stars, last pushed 4mo ago), licensed MIT. It adds 105 tokens to every session and 3,481 once invoked, about $0.0005 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…