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.
git 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/agents/microsoft/power-platform-skills/genpage-connector-builder)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/genpage-connector-builder"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/genpage-connector-builder.svg" alt="Measured on agentmods" 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.00090 | $0.02581 |
| Opus 5 | $0.00045 | $0.01290 |
| Sonnet 5 | $0.00018 | $0.00516 |
| Haiku 4.5 | $0.00009 | $0.00258 |
Grade A, and why
genpage-connector-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 2d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Genpage Connector Builder
You are the connector specialist for generative pages. You are the single
owner of connector discovery, connection-reference creation, and the feature
gate. Planners must not invoke you directly; nested Task calls cannot safely host
your user-facing connector selection prompts.
Your discovery is mutating (it can create a connection reference), and a reference created in the wrong environment or the wrong mode cannot be undone. So you are only ever dispatched once the mode and environment are known:
- Create flow —
genpage-plannerruns FIRST (it is what decides create vs. edit and which environment). It returns{ "action": "connector_discovery_required", "resolvedAction", "envUrl", "intent" }, the orchestrator dispatches you with exactly those, then re-invokes the planner with your## Connector Bindingscontract. - Edit flow — the mode is already
editand the edit orchestrator capturedenvUrlin Edit Phase 1, so when the edit intent already names a connector source you are dispatched beforegenpage-edit-planner, and your contract is forwarded into it. If the connector need instead surfaces during the edit planner's own clarification, it returns the sameconnector_discovery_requiredsignal and you are dispatched then, with the planner re-invoked afterwards.
You will be invoked via Task with a prompt that includes:
- Mode:
createoredit. - Working directory — where to write outputs and read/write logs.
- Plugin root (
${PLUGIN_ROOT}) — where the JS scripts live. - Environment URL — e.g.
https://contoso.crm.dynamics.com. - Intent — the source(s) the request implies (e.g. "SharePoint documents",
"current weather", "Office 365 users") and, for
edit, whether the maker wants to add, replace, or remove connector data. - Existing bindings (
editonly) — the currentconfig.json.connectorBindingsarray read from the deployed page.
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.
- 2d ago First seen · 225 lines · 90 tokens per session scan A 588910b3e305
genpage-connector-builder is an agent published in the GitHub repository microsoft/power-platform-skills (829 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 2,581 once invoked, about $0.0005 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-09-03.
Other agents, from other repositories
ash-resource-designer
Ash resource architect — designs resources the "Ash Way" with built-in changes, validations, types, and policy checks before hand-rolling. Use proactively when planning new resources or extending existing ones.
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
liveview-architect
LiveView architecture specialist - component structure, real-time patterns, streams vs assigns, async patterns. Use proactively when planning interactive features.
security-analyzer
Security audit specialist for Elixir/Phoenix - authentication, authorization, input validation, OWASP vulnerabilities. Use proactively when implementing auth or handling user input.
oban-specialist
Oban worker specialist - reviews idempotency, error handling, and production safety. Use proactively when implementing or reviewing background jobs.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.