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 skills add microsoft/power-platform-skills --skill author-webpage-contentgit 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/skills/microsoft/power-platform-skills/author-webpage-content)<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/author-webpage-content"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/author-webpage-content/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/skills/microsoft/power-platform-skills/author-webpage-content"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/author-webpage-content.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.00163 | $0.02473 |
| Opus 5.5 | $0.00065 | $0.00989 |
| Sonnet 5.5 | $0.00033 | $0.00495 |
| Haiku 4.5 | $0.00016 | $0.00247 |
Grade A, and why
author-webpage-content 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- typescript — 88% identical, 338 lines differ
- typescript — 84% identical, 337 lines differ
- typescript — 80% identical, 334 lines differ
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin check: Run
node "${PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
Author Webpage Content
Generate and fill one supplied localized Design Studio-compatible webpage body.
Initial request: $ARGUMENTS
Preview disclosure
Read ${PLUGIN_ROOT}/references/non-spa-preview.md and apply its Entry and handoff
protocol. Unless the initial request contains the explicit marker from an actual covered-skill
handoff, present the Customization notice before project inspection or task creation.
Authoritative references
Always read and follow:
${PLUGIN_ROOT}/skills/author-webpage-content/references/webpage-content-composition.md${PLUGIN_ROOT}/skills/author-webpage-content/references/design-studio-component-authoring.md
Read only the page-element references used by the requested composition:
design-studio-section-layouts.mddesign-studio-flex-container-component.mddesign-studio-text-component.mddesign-studio-image-component.mddesign-studio-button-component.mddesign-studio-video-component.mddesign-studio-iframe-component.mddesign-studio-generative-ai-search-component.mddesign-studio-basic-form-component.mddesign-studio-list-component.mddesign-studio-multistep-form-component.mddesign-studio-spacer-component.md
All page-element references are under:
${PLUGIN_ROOT}/skills/author-webpage-content/references/
These references own serialized section and component markup, editing boundaries, preservation, accessibility, and verification rules. Do not invent competing markup contracts.
For an add or edit Generative AI Search component request, target only
{% codecomponent name:Pages.SearchSummary ... %}. Do not substitute
{% include 'Search' %}, a Search web template, Search content snippets, the
Search Results page record, site markers, or search indexing/settings.
For an add or edit Basic Form, List, or Multistep form request, target only
{% entityform name:'...' %}, {% include 'entity_list' key:'...' ... %}, or
{% webform name:'...' %} respectively, pointing at a record already present in
the downloaded site. This skill does not create the backing basic form, list,
multistep form, Dataverse table form/view, or table permissions — see each
component reference's Scope section. If the named (or implied) record is
not found in the downloaded site, do not assist with constructing it: do not
query Dataverse (API, SDK, Web API, or CLI) and do not ask the user for IDs,
GUIDs, or permissions to assemble it locally. When asking the user how to
proceed, the only valid options are (a) embed an existing record, or (b) stop.
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/design-studio-basic-form-component.md 4.5 KB
- references/design-studio-button-component.md 10 KB
- references/design-studio-component-authoring.md 4.3 KB
- references/design-studio-flex-container-component.md 4.2 KB
- references/design-studio-generative-ai-search-component.md 5.4 KB
- references/design-studio-iframe-component.md 8.0 KB
- references/design-studio-image-component.md 11 KB
- references/design-studio-list-component.md 5.6 KB
- references/design-studio-multistep-form-component.md 5.1 KB
- references/design-studio-section-layouts.md 12 KB
- references/design-studio-spacer-component.md 7.9 KB
- references/design-studio-text-component.md 8.8 KB
- references/design-studio-video-component.md 11 KB
- references/webpage-content-composition.md 14 KB
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 · 268 lines · 163 tokens per session scan A b971fb0be00e
author-webpage-content is a skill published in the GitHub repository microsoft/power-platform-skills (1,061 stars, last pushed today), licensed MIT. It adds 163 tokens to every session and 2,473 once invoked, about $0.0007 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-10-25.
Other skills, from other repositories
canvas-apps-ui-gen
Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.
fec-drawio-studio
An editable workflow for making technical diagrams in draw.io (also called diagrams.net), with the original .drawio file saved alongside exported images or documents. It covers architecture, database, UML, sequence, flow, machine-learning, and code-structure diagrams.
fec-nextjs-project-standard
A development guide for Next.js 14 and newer projects using App Router, Next.js’s file-based routing system. It covers server-rendered pages, layouts, data loading, middleware, metadata, and server actions.
fec-state-management
A guide for deciding where an application's changing information should live, such as inside a component, in the URL, in a form, in a browser cache, or in a shared store. A store is a shared place for client-side information used across parts of an app.
fec-component-testing
A guide for writing and reviewing front-end unit, component, and lightweight integration tests. These tests check small pieces of code and UI behavior without running a full browser journey.
fec-monorepo-project-standard
A guide for organising a monorepo, which is one code repository containing several applications and shared packages. It covers workspace dependencies, folder structure, build tasks, testing, caching, and package releases.