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 Mr-M-tastic/Power-Automate-MCP --skill manage-runsgit clone --depth 1 https://github.com/Mr-M-tastic/Power-Automate-MCPWrote 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/mr-m-tastic/power-automate-mcp/manage-runs)<a href="https://agentmods.dev/skills/mr-m-tastic/power-automate-mcp/manage-runs"><img src="https://agentmods.dev/badge/skills/mr-m-tastic/power-automate-mcp/manage-runs/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/mr-m-tastic/power-automate-mcp/manage-runs"><img src="https://agentmods.dev/badge/skills/mr-m-tastic/power-automate-mcp/manage-runs.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.00073 | $0.00400 |
| Opus 5 | $0.00036 | $0.00200 |
| Sonnet 5 | $0.00015 | $0.00080 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
manage-runs 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.
What it actually says
Manage Flow Runs & Lifecycle
Handle the following lifecycle/run request:
$ARGUMENTS
Capabilities
| Intent | Tool | Notes |
|---|---|---|
| Enable a flow | turn_on_flow |
|
| Disable a flow | turn_off_flow |
|
| List recent runs | list_runs |
Returns run ids, status, start time |
| Resubmit a run | resubmit_run { trigger, runId } |
trigger is the trigger name (often manual) |
| Cancel a run | cancel_run { runId } |
Only running flows can be cancelled |
Workflow
- If no session is set, run
/configure-pa-flow-mcpfirst. - For resubmit/cancel, call
list_runsfirst to find therunIdand (for resubmit) the trigger name. - Confirm destructive actions (cancel) with the user before calling.
- Report the resulting status.
Notes
- Resubmit reuses the original trigger inputs — it does not let you change them.
- A disabled flow won't run on its trigger until turned back on.
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 · 37 lines · 73 tokens per session scan A 388c01b0ec3f
manage-runs is a skill published in the GitHub repository Mr-M-tastic/Power-Automate-MCP (1 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 400 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…