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-monitoringgit 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-monitoring)<a href="https://agentmods.dev/skills/ninihen1/power-automate-mcp-skills/flowstudio-power-automate-monitoring"><img src="https://agentmods.dev/badge/skills/ninihen1/power-automate-mcp-skills/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/ninihen1/power-automate-mcp-skills/flowstudio-power-automate-monitoring"><img src="https://agentmods.dev/badge/skills/ninihen1/power-automate-mcp-skills/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 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.
This is a copy
100% identical to flowstudio-power-automate-monitoring — 4 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 — 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
FlowStudio 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.
- 12d ago First seen · 374 lines · 105 tokens per session scan A 0a4055296428
flowstudio-power-automate-monitoring is a skill published in the GitHub repository ninihen1/power-automate-mcp-skills (32 stars, last pushed 8d 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. It is 100% identical to flowstudio-power-automate-monitoring, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
datarobot-workload-api
Use when the user wants to create, configure, scale, debug, observe, or roll out container workloads on DataRobot's Workload API. Triggers include: deploying a container as a managed service, listing/starting/stopping workloads, changing replica counts or autoscaling, picking CPU/GPU compute bundles, injecting…
forge-cost-optimizer
Optimizes Atlassian Forge apps to reduce platform consumption and avoid unnecessary costs using Atlassian's "Optimise Forge platform costs" guidance. Use when the user asks to optimize Forge app costs, reduce Forge invocations, lower GB-seconds, reduce storage or log usage, tune memory, replace polling, improve…
upstash-qstash-js
Work with the @upstash/qstash TypeScript/JavaScript SDK, an HTTP-based message queue, task scheduler, and background job system for serverless and edge runtimes (Next.js, Vercel, Cloudflare Workers, Deno, Node.js). Use when publishing messages to HTTP endpoints or URL groups, running background jobs without a…
upstash
Work with any Upstash product, SDK, or tool, including serverless Redis (caching, sessions, leaderboards, key-value storage), Ratelimit (rate limiting and throttling), QStash (message queue, cron schedules, background jobs), Workflow (durable long-running functions), Vector (vector database for embeddings, semantic…
upstash-box-remote-work
Do work in an Upstash Box, a sandboxed cloud container driven through the remote Upstash MCP server (mcp.upstash.com), instead of on the local machine. Use when the user asks to run, build, test, clone, or edit something remotely, in a sandbox, in the cloud, or in a box, when the deliverable is a pull request, a…
canary-watch
Post-deploy monitoring and canary health verification.