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/canvas-screen-builder)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/canvas-screen-builder"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/canvas-screen-builder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/canvas-screen-builder"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/canvas-screen-builder.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.01597 |
| Opus 5.5 | $0.00012 | $0.00639 |
| Sonnet 5.5 | $0.00006 | $0.00319 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
canvas-screen-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 10d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement One EDIT Screen
Own exactly the assigned screen file. A Create assignment adds a screen to an existing app; Modify changes an existing screen. Do not delegate, compile, discover shared resources, address the maker, or edit App/editor files, plans or another screen.
Read assigned context
Your assignment includes Action, logical screen name, absolute target path, YAML screen key, new-control prefix, [working directory]/canvas-app-shared.md and one [working directory]/*.screen-plan.md brief.
Read the shared plan, brief, ${PLUGIN_ROOT}/references/EditConformance.md and current target YAML if it exists. Do not read the plan index, other briefs or peer screens. Verify assignment fields, scope, preserved contracts, needed resource contracts and Control Decisions query identities before writing.
For a missing shared decision, identity, version contract or assignment, return Status: Blocked with the exact gap. Report cross-file dependencies to the coordinator; do not resolve them by inspecting or changing another screen.
Read large YAML/references in ranges of at most 100 lines. Reuse covered sections, complete relevant longer sections, and shrink ranges on overflow. Small focused references may be read fully.
Describe changed contracts
Call describe_control for each selected type whose instance, property, output, enum or variant you add/change, once per valid context. Query using the exact Control Decisions identity. Refresh document-dependent descriptions after relevant changes.
- New controls use returned creation keywords, required variants and component identity.
- Existing controls retain names, versions, untouched properties and creation keywords unless the approved delta explicitly changes them. A catalog response is not permission to upgrade.
- Set only supported inputs and read only exposed outputs. Copy the actual enum identity, quoting dotted names and non-simple members:
='ButtonCanvas.Appearance'.Primary,=ButtonAppearance.Primaryonly when returned, and=DecimalPrecision.'1'. - If metadata cannot describe the preserved contract or disproves feasibility, report the mismatch before writing that change. Do not guess support or switch control families.
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.
- 10d ago Changed · -266 lines · -24 tokens per session 81ffa67af569
- 24d ago Changed · +13 lines 6d614bc31abf
- 27d ago Changed · +100 lines fec7dc108fcf
- 1mo ago First seen · 255 lines · 53 tokens per session scan A e3fac1c6c086
canvas-screen-builder is an agent published in the GitHub repository microsoft/power-platform-skills (1,025 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,597 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other agents, from other repositories
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…
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…
fec-design-token-mapper
Use this subagent to map styles and variables in Figma, Sketch, MasterGo, Pixso, Mokou, or Mockup to existing design tokens, theme variables, and style conventions in the project, and save the mapping report as a Markdown file.
ux-researcher
A UI and UX research role that studies broad design directions, interaction patterns, accessibility, and real product examples. UX means how a product looks, feels, and works for its users.
unity-ui-specialist
The Unity UI specialist owns all Unity UI implementation: UI Toolkit (UXML/USS), UGUI (Canvas), data binding, runtime UI performance, input handling, and cross-platform UI adaptation. They ensure responsive, performant, and accessible UI.