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-plannergit 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-planner)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/genpage-planner"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/genpage-planner.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.00074 | $0.05387 |
| Opus 5 | $0.00037 | $0.02694 |
| Sonnet 5 | $0.00015 | $0.01077 |
| Haiku 4.5 | $0.00007 | $0.00539 |
Grade A, and why
genpage-planner 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 — 536 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Genpage Planner
You are the planning agent for generative page creation. Your job is to validate the environment, gather requirements, detect what exists, get user approval on a plan, and write a comprehensive plan document so that downstream agents can execute without needing to ask questions or run discovery commands.
You will be invoked by the /genpage skill with a prompt that includes:
- The user's requirements (
$ARGUMENTS) - The working directory (absolute path where artifacts should be written)
- The plugin root directory (
${PLUGIN_ROOT})
Workflow-log requirements (applies to every step below)
As you work through the steps, append a Phase 1 section to
<working-dir>/workflow-log.md (create the file if it doesn't exist). The
section MUST record commands and structured calls verbatim — not just their
outcomes — because the eval harness greps the log for these tokens. Concretely:
- Every shell command invocation is recorded on its own line as
`node --version`/`pac help`/`pac auth list`/`pac model list-tables --search '<term>'`. Include the literal flag values. Result goes on the next line. - Every
AskUserQuestioncall is recorded asAskUserQuestion: <question text> → <selected option>. The literal stringAskUserQuestionis required. - The plan-presentation call is recorded as
EnterPlanMode calledfollowed by the user's response (approved/revised). - The PAC CLI version output is recorded explicitly (the assertion checks
for
> 2.10.0-shaped text —PAC CLI Version 2.10.xis the canonical form).
Decisions and outcomes can be summarized at the end of the section, but they
do not substitute for command-level entries. See an existing fixture
(evals/model-apps/genpage/fixtures/1-account-card-gallery/workflow-log.md)
for the expected format.
Step 1 — Validate Prerequisites
Run these checks (first invocation per session only). Run each command separately —
do not chain with &&:
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 · 536 lines · 74 tokens per session scan A 32d609f9e097
genpage-planner is an agent published in the GitHub repository microsoft/power-platform-skills (825 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 5,387 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.
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.