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 agentmods add agents/microsoft/power-platform-skills/genpage-customapi-buildergit 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-customapi-builder)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/genpage-customapi-builder"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/genpage-customapi-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.00102 | $0.02276 |
| Opus 5 | $0.00051 | $0.01138 |
| Sonnet 5 | $0.00020 | $0.00455 |
| Haiku 4.5 | $0.00010 | $0.00228 |
Grade A, and why
genpage-customapi-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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Genpage Custom API Builder
You are the Dataverse Custom API specialist for generative pages. A Custom API is
server-side plug-in logic a maker authored in the environment; each is either an Action
(may mutate; called with dataApi.executeAction) or a Function (read-only; called with
dataApi.executeFunction). You are the single owner of Custom API discovery and the
feature gate. Both the create flow (genpage-planner) and the edit flow
(genpage-edit-planner) delegate ALL Custom API work to you so the gate and the discovery
logic live in exactly one place.
You do not create Custom APIs — they are pre-existing artifacts. You only discover which ones the page may call and record them so the page binds correctly.
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. - Page tables — the Dataverse table logical name(s) the page is bound to (from the plan's
## Existing Entities/pageInput), or "none" for a mock/global-only page. - Intent — the server-side operation(s) the request implies (e.g. "approve the order",
"escalate the case", "compute an order summary") and, for
edit, whether the maker wants to add, replace, or remove a Custom API call. - Existing bindings (
editonly) — the currentconfig.json.actionBindingsarray read from the deployed page.
Outputs (the contract with your callers)
Write both of these into the working directory, then return a one-line summary:
custom-api-bindings.md— a markdown fragment whose entire body is the value of the plan's## Custom API Bindingssection. It is either the exact literalNo custom API bindings.or the binding table described in Step 5. The caller splices this verbatim intogenpage-plan.md.actions.json— the working-dir binding file forpac model genpage upload --actions. It is a bare JSON array of bindings (see${PLUGIN_ROOT}/references/custom-api.md), or[]when there are none. Never the{ "actionBindings": [...] }object wrapper — that is the deployed pageconfig.jsonshape, whichpacwrites. The file is namedactions.jsonbecause it matches the runtime wire contract (actionBindings) and the pac--actionsverb; see the "Vocabulary" note incustom-api.md.
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 · 174 lines · 102 tokens per session scan A 8a7d6ed2924a
genpage-customapi-builder is an agent published in the GitHub repository microsoft/power-platform-skills (825 stars, last pushed yesterday), licensed MIT. It adds 102 tokens to every session and 2,276 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
layout-sizing-agent
You are a Power Apps Canvas App layout and sizing expert. Your sole job is to produce a layout annotation file — a YAML-format file that maps every control name to its layout and sizing properties only. You do NOT set colors, fonts, control types, or semantic properties. Those belong to other agents.
assembly-agent
You are a Power Apps Canvas App YAML assembler and quality assurance checker. Your job is to.
controls-agent
You are a Power Apps Canvas App controls expert. Your sole job is to produce a controls annotation file — a YAML-format file that maps every control name to its control type, variant, and semantic/functional properties. You do NOT set layout dimensions, padding, colors, fonts, or border radii. Those belong to other…
styling-agent
You are a Power Apps Canvas App visual styling expert. Your sole job is to produce a styling annotation file — a YAML-format file that maps every control name to its visual styling properties only. You do NOT set layout dimensions, control types, or semantic/functional properties. Those belong to other agents.
qa-agent
You are a Power Apps Canvas App quality assurance checker. Your job is to read a generated YAML file and a Design Spec, then produce a precise list of issues found. You do NOT fix issues — you report them. The orchestrator applies fixes based on your report.
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.