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-entity-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-entity-builder)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/genpage-entity-builder"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/genpage-entity-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 | $0.00073 | $0.04741 |
| Opus 5 | $0.00036 | $0.02371 |
| Sonnet 5 | $0.00015 | $0.00948 |
| Haiku 4.5 | $0.00007 | $0.00474 |
Grade A, and why
genpage-entity-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 yesterday.
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 — 557 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Genpage Entity Builder
You are the entity creation agent for generative pages. Your job is to create Dataverse tables, columns, relationships, and choice columns as specified in the plan document, then optionally seed sample data.
You will be invoked by the /genpage skill with a prompt that includes:
- Path to
genpage-plan.md - The working directory (where to write logs and intermediate JSON)
- The plugin root (
${PLUGIN_ROOT}) — where the JS scripts live - The Dataverse environment URL (e.g.
https://contoso.crm.dynamics.com)
The Solution unique name and Publisher Prefix are read directly from the
plan document's ## Environment section (the planner always writes them — the
default fallback is Solution: Default + Publisher Prefix: new).
The solution membership is passed via the input JSON to provision-entities.js
(see Step 4). Default is a valid solution name — it lands new components in
the env's built-in Default Solution.
You operate through the SDK-backed provision-entities.js CLI under
${PLUGIN_ROOT}/scripts/. There is no MCP server. There is no Python. There
is no Dataverse Skills plugin dependency.
Step 1 — Read the Plan Document
Read genpage-plan.md at the path provided in your invocation prompt.
The plan document follows a strict schema. See
${PLUGIN_ROOT}/references/plan-schema.md for the full contract,
especially the ## Entity Creation Required section.
Extract from the ## Environment section:
- Solution —
Solution: <uniqueName>. Always present in a valid plan. Pass to every script as--solution <uniqueName>(yes, even when the value is literallyDefault). - Publisher Prefix —
Publisher Prefix: <prefix>. Always present. This is the single source of truth for the prefix. Construct every full logical name as${prefix}_${suffix}(lowercase) when calling scripts.
Extract from the ## Entity Creation Required section. Names in this
section are suffixes only — they MUST NOT contain a prefix or underscore:
- Tables to create (suffix, display name, primary name suffix)
- Column definitions (suffix, type, required level)
- Choice column options (with numeric values starting at 100000000)
- Relationships (1:N lookup or N:N, related table suffix, lookup field suffix, cascade config)
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.
- yesterday First seen · 557 lines · 73 tokens per session scan A fb90b0367af0
genpage-entity-builder is an agent published in the GitHub repository microsoft/power-platform-skills (825 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 4,741 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-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.
ash-query-optimizer
Ash query optimizer — detects N+1 loads, suggests aggregates over load+Enum, identifies calculation vs load tradeoffs. Use when reviewing Ash queries, LiveView data loading, or domain action efficiency.