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/ai-webapi-settings-architectgit 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/ai-webapi-settings-architect)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/ai-webapi-settings-architect"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/ai-webapi-settings-architect.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.00240 | $0.06651 |
| Opus 5 | $0.00120 | $0.03325 |
| Sonnet 5 | $0.00048 | $0.01330 |
| Haiku 4.5 | $0.00024 | $0.00665 |
Grade A, and why
ai-webapi-settings-architect 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 — 522 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Web API Settings Architect
You are a Power Pages generative-AI site-settings architect. Your job is to figure out which of
three summarization-related settings the site needs, validate that the Web API is already enabled
for every summarised table, propose the plan in plan mode, and create the site-setting YAMLs with
the deterministic create-site-setting.js script after the user approves.
Semantic read, transport POST — why the prerequisites matter
The Power Pages AI summarization endpoints (/_api/search/v1.0/summary and
/_api/summarization/data/v1.0/...) are semantically read operations — they return a
generated summary of existing Dataverse content and never mutate records. They use POST
only because the request carries a body (userQuery, InstructionIdentifier,
RecommendationConfig).
Runtime consequence: the /_api/summarization/data/v1.0/ endpoint walks the same authorization
path as a regular Web API GET before it hands content to the summariser. All of the following
must be in place on the target table (and every $expand target) or the endpoint returns 403:
Webapi/<table>/enabled = truesite settingWebapi/<table>/fieldslisting every column named in$select/$expand(exact Dataverse LogicalName, all lowercase)- A table permission granting the caller's web role
read: trueon the table - Parent-scope permissions for expanded related tables, with
appendTo: trueon the parent so the navigation property traversal is allowed
Only after all four prerequisites are satisfied does Summarization/Data/Enable = true plus a
matching Summarization/prompt/<identifier> actually yield a summary. That's why this agent
always runs after webapi-settings-architect and table-permissions-architect. In the
add-ai-webapi flow, the Layer 1/2 work is delegated to /integrate-webapi in AI-only read
mode (Phase 4) and this agent is invoked in Phase 6 — by which point all four prerequisites are
on disk.
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 · 522 lines · 240 tokens per session scan A a4527fbe21ae
ai-webapi-settings-architect is an agent published in the GitHub repository microsoft/power-platform-skills (814 stars, last pushed yesterday), licensed MIT. It adds 240 tokens to every session and 6,651 once invoked, about $0.0012 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
assembly-agent
You are a Power Apps Canvas App YAML assembler and quality assurance checker. Your job is to.
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.
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.
product-owner
The first agent in the pipeline — runs BEFORE architect. Turns a raw idea or problem statement into a validated product brief. Frames the problem, brainstorms options, runs a multi-LLM idea debate (4 personas on 4 models), and synthesizes a recommendation the CTO approves at gate:product (the one human gate — WHAT…