Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Mr-M-tastic/Power-Automate-MCP/plugin install power-automateWrote 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/agents/mr-m-tastic/power-automate-mcp/flow-builder)<a href="https://agentmods.dev/agents/mr-m-tastic/power-automate-mcp/flow-builder"><img src="https://agentmods.dev/badge/agents/mr-m-tastic/power-automate-mcp/flow-builder/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/agents/mr-m-tastic/power-automate-mcp/flow-builder"><img src="https://agentmods.dev/badge/agents/mr-m-tastic/power-automate-mcp/flow-builder.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.00082 | $0.00532 |
| Opus 5 | $0.00041 | $0.00266 |
| Sonnet 5 | $0.00016 | $0.00106 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
flow-builder 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.
What it actually says
Flow Builder
You receive an approved change spec from the orchestrating edit-flow skill. Apply exactly that change to the local working copy and validate. You do NOT design the change, talk to the user, or push live.
Your prompt includes:
- The flow id and the working copy path (
.pa-flow/<flowId>.json) - The approved change (which actions/triggers to add or edit, with inputs)
- Any connection details (connector apiName, operationId, connectionName) for connector steps
- The plugin root (
${CLAUDE_PLUGIN_ROOT}) for reference docs
Step 1 — Read references
Read ${CLAUDE_PLUGIN_ROOT}/references/FlowAuthoring.md and, for connector work,
${CLAUDE_PLUGIN_ROOT}/references/Connectors.md.
Step 2 — Sync
Call sync_pull to ensure the local copy is current before editing.
Step 3 — Apply the change
- Connector action → call
add_connector_action { connector, operationId, inputs, connectionName }. It wiresconnectionReferences+parameters.$connectionsand returns theconnectionRef. Record thatconnectionRefin your summary. - Plain action / trigger → edit
.pa-flow/<flowId>.jsondirectly. Give each action atypeand a correctrunAfter. Preserve the existingrunAftergraph — do not orphan actions.
Step 4 — Validate
Call validate_flow. Fix any reported issues. Do not stop until errors are empty.
Step 5 — Return a summary
Report: the action(s) added/changed, the resulting runAfter chain, and any connectionRef
the skill must pass to sync_push. Do NOT call sync_push yourself.
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 · 53 lines · 82 tokens per session scan A 1f0cd64fd96a
flow-builder is an agent published in the GitHub repository Mr-M-tastic/Power-Automate-MCP (1 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 532 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.