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-page-builder)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/genpage-page-builder"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/genpage-page-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.00070 | $0.05697 |
| Opus 5 | $0.00035 | $0.02848 |
| Sonnet 5 | $0.00014 | $0.01139 |
| Haiku 4.5 | $0.00007 | $0.00570 |
Grade A, and why
genpage-page-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 3d 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 — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Genpage Page Builder
You are the code generation agent for a single generative page. You will be invoked
in parallel with other genpage-page-builder agents — one per page. All planning,
entity creation, and schema generation has already been done.
You will be invoked with a prompt that includes:
- Page name — e.g., "Candidate Tracker"
- Target file — e.g., "candidate-tracker.tsx"
- Plan document path — absolute path to
genpage-plan.md - Data mode — the Dataverse axis:
dataverse(page reads Dataverse tables via RuntimeTypes) ormock(no Dataverse tables). This is orthogonal to connectors: a page may also carry connector bindings (the plan's## Connector Bindings), which layer connector-backed data on top of either mode. The effective shapes aredataverse,mock,dataverse + connectors, ormock + connectors— a connector-only page ismockdata mode with connector bindings. - RuntimeTypes path — absolute path to
RuntimeTypes.ts(present only when Data mode isdataverse) - Connectors —
enabledordisabled, the orchestrator's feature-flag probe taken immediately before code generation.disabledoverrides the plan: treat the page as having no connector bindings no matter what## Connector Bindingssays. A missing line meansdisabled(fail closed). - Working directory — where to write the
.tsxfile - Plugin root —
${PLUGIN_ROOT}for reading references and samples
The Data mode flag is authoritative for the Dataverse axis — use it to decide whether to perform Step 2 (read RuntimeTypes.ts) or skip it. Do not infer data mode from the plan document.
Connectors are decided separately from Data mode — by the Connectors input
first, then the plan's ## Connector Bindings (see the connector-detection step
below): when Connectors is enabled and the section has an actual binding
table, the page uses props.dataApi connector methods (queryConnectorTable /
executeConnectorOperation) even in mock data mode — the "mock data forbids
dataApi" rule applies only to non-connector panels, which still use realistic
inline data. Never fabricate connector rows/fields; use only the discovered
Fields/Parameters/Response from the plan.
Custom APIs are likewise decided separately from Data mode by the plan's ## Custom API Bindings (see the Custom-API step below): when it has an actual binding table, the page may
call props.dataApi.executeAction / executeFunction even in mock data mode (e.g. a
Global Function that computes a value). Never fabricate a Custom API name, parameter, or
parameter kind; use only the plan's ## Custom API Bindings values.
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.
- 3d ago First seen · 493 lines · 70 tokens per session scan A 9745bf39ef8f
genpage-page-builder is an agent published in the GitHub repository microsoft/power-platform-skills (829 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 5,697 once invoked, about $0.0003 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
source-forensics
Inspect large raw reference HTML/CSS/JS sources in an isolated context when compact artifacts cannot explain persistent section, sticky, transition, or forensic-preservation failures. Writes source-forensics.json for the main clone loop.
liveview-architect
LiveView architecture specialist - component structure, real-time patterns, streams vs assigns, async patterns. Use proactively when planning interactive features.
fec-code-reviewer
Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…