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
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 microsoft/power-platform-skills --skill add-connectorgit clone --depth 1 https://github.com/microsoft/power-platform-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/microsoft/power-platform-skills/add-connector)<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/add-connector"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/add-connector/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/add-connector"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/add-connector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00027 | $0.01246 |
| Opus 5 | $0.00014 | $0.00623 |
| Sonnet 5 | $0.00005 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
add-connector 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns.
Add Connector (Generic)
Fallback skill for any connector not covered by a specific /add-* skill. For common connectors, prefer the dedicated skills:
/add-dataverse-- Dataverse tables/add-azuredevops-- Azure DevOps/add-teams-- Microsoft Teams/add-excel-- Excel Online (Business)/add-onedrive-- OneDrive for Business/add-sharepoint-- SharePoint Online/add-office365-- Office 365 Outlook (calendar, email, contacts)/add-workiq-- Work IQ (M365 Copilot Search)
Workflow
- Check Memory Bank → 2. Identify Connector → 3. Add Connector → 4. Inspect & Configure → 5. Build → 6. Update Memory Bank
Step 1: Check Memory Bank
Check for memory-bank.md per shared-instructions.md.
Step 2: Identify Connector
If $ARGUMENTS is provided or the caller already specified the connector, use it directly and skip the question below.
Otherwise, ask the user which connector they want to add. Browse available connectors: Connector Reference
Before proceeding, check if the connector has a dedicated skill. If it does, delegate immediately and STOP:
| Connector API name | Delegate to |
|---|---|
shared_a365copilotchatmcp |
/add-workiq |
sharepointonline |
/add-sharepoint |
teams |
/add-teams |
excelonlinebusiness |
/add-excel |
onedriveforbusiness |
/add-onedrive |
azuredevops |
/add-azuredevops |
office365 |
/add-office365 |
commondataservice |
/add-dataverse |
Invoke the appropriate skill with the same $ARGUMENTS and do not continue this skill's workflow.
Common connector API names:
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 · 116 lines · 27 tokens per session scan A c80f64b13844
add-connector is a skill published in the GitHub repository microsoft/power-platform-skills (844 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,246 once invoked, about $0.0001 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-30.
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.
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
oban
Oban job processing — workers, perform/1 (OSS) and process/1 (Pro), queues, cron, retries, unique jobs, idempotency, Oban Pro (Workflow, Batch, Chunk, Smart Engine), Testing. Use when writing Oban workers, queue config, or debugging jobs.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.