microsoft/power-platform-skills is a plugin marketplace containing reusable skills, agents, and commands for developing with Microsoft Power Platform. Developers use it to build and deploy Power Pages sites, model-driven Power Apps, and related solutions through Claude Code or GitHub Copilot. The catalogue entries are the marketplace's included skills, agents, plugins, and other agent components.
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 microsoft/power-platform-skills/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/skills/microsoft/power-platform-skills/setup)<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/setup"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/setup/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/microsoft/power-platform-skills/setup"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/setup.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.00028 | $0.03558 |
| Opus 5.5 | $0.00011 | $0.01423 |
| Sonnet 5.5 | $0.00006 | $0.00712 |
| Haiku 4.5 | $0.00003 | $0.00356 |
Grade A, and why
setup 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 27d 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.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First-Time Setup Guide
You are helping a non-technical user get the Power Automate plugin working for the first time. Be friendly, use plain language, and never assume they know terminal commands. Walk them through each step one at a time.
Step 1: Check Node.js
Run silently:
node --version 2>&1
- If it works (prints something like
v18.x.xor higher): Tell them "Node.js is installed" and move on. - If it fails or version is below 18: Tell them they need Node.js 18 or newer. Ask what operating system they're on, then give them the simplest install instructions:
- Windows: "Go to https://nodejs.org, download the LTS version, and run the installer. Click Next through everything."
- Mac: "Open Terminal and run:
brew install node" (or direct them to nodejs.org) - After they've installed it, re-check with
node --version.
Step 2: Check Azure CLI
Run silently:
az --version 2>&1
- If it works: Tell them "Azure CLI is installed" and move on.
- If it fails: Tell them they need the Azure CLI. Ask their OS:
- Windows: "Open PowerShell as administrator and run:
winget install Microsoft.AzureCLI" or direct them to https://aka.ms/installazurecliwindows - Mac: "
brew install azure-cli" - After install, re-check with
az --version.
- Windows: "Open PowerShell as administrator and run:
Step 3: Azure Login
Check if they're already logged in:
az account show --output json 2>&1
- If it works (shows account info): Tell them who they're logged in as (show the
user.namefield) and ask if that's the right account. - If it fails: Tell them "Let's sign you into Azure." Then run:
This will open their browser. Tell them: "A browser window should open. Sign in with your work account — the one you use for Power Automate." After login completes, confirm it worked by runningaz loginaz account showagain.
Verify token access — this catches permission issues early.
First find out which Azure cloud they're on, because the Power Automate resource URL differs per cloud and the commercial one cannot be assumed (GCC High / DoD tenants will fail against it):
az cloud show --query name -o tsv
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.
- 27d ago Changed · +54 lines d01660046f4c
- 1mo ago First seen · 156 lines · 28 tokens per session scan A fd3cf9860f62
setup is a skill published in the GitHub repository microsoft/power-platform-skills (1,025 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 3,558 once invoked, about $0.0001 per session on Opus 5.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
canvas-apps-ui-gen
Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
ux-heuristics
Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "users are confused", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "is this easy to use". Also trigger when reviewing a design for usability issues, improving…
blue-ocean-strategy
Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war".…
clean-code
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a…
session-scan
Compute metrics for Claude Code sessions. Discovers via ccrider, filters trivial, computes friction/opportunity/fingerprint scores. Use for broad session triage.