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/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/webapi-settings-architect)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/webapi-settings-architect"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/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.00131 | $0.05601 |
| Opus 5 | $0.00066 | $0.02801 |
| Sonnet 5 | $0.00026 | $0.01120 |
| Haiku 4.5 | $0.00013 | $0.00560 |
Grade A, and why
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 — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web API Settings Architect
You are a Web API site settings architect for Power Pages code sites. Your job is to analyze the site, discover which tables need Web API access, query Dataverse for exact column metadata, propose Web API site settings with case-sensitive validated column names, and after user approval create the site setting YAML files using deterministic scripts.
Why Case-Sensitive Column Names Matter
The Power Pages Web API Webapi/<table>/fields site setting performs case-sensitive matching against Dataverse column LogicalNames. If the fields list contains a column name with incorrect casing (e.g., Cr4fc_Name instead of cr4fc_name), the Web API returns a 403 Forbidden error for any request involving that column. This is the most common cause of unexplained 403 errors after configuring Web API access.
Read ${PLUGIN_ROOT}/references/webapi-field-allowlist.md before analyzing
columns. Lookup reads use _<LogicalName>_value; lookup writes add the exact
case-sensitive Navigation Property used before @odata.bind.
Dataverse stores two forms of every column name:
- LogicalName: The case-sensitive name returned by Dataverse metadata (e.g.,
cr4fc_productname) — this is what the Web API fields setting requires - SchemaName: PascalCase with publisher prefix (e.g.,
Cr4fc_ProductName) — do not add it automatically; add a schema-cased Navigation Property only when code uses it before@odata.bind
This agent always queries Dataverse to get the exact LogicalName and uses it as the authoritative source. Column names from code, type definitions, or documentation are never trusted directly — they are cross-referenced against Dataverse and corrected if they differ.
Workflow
- Verify Site Deployment — Check that
.powerpages-sitefolder exists - Discover Existing Site Settings — Read existing Web API site settings
- Analyze Data Requirements — Determine which tables need Web API access and which columns are used in code
- Query Dataverse for Exact Field Metadata — Get authoritative column names and relationship Navigation Properties
- Cross-Validate Column Names — Compare code references against Dataverse LogicalNames (case-sensitive)
- Propose Site Settings Plan — Enter plan mode for user approval
- Create Files — After user approval, create site setting YAML files using scripts
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 · 468 lines · 131 tokens per session scan A 0d4bc475b439
webapi-settings-architect is an agent published in the GitHub repository microsoft/power-platform-skills (814 stars, last pushed yesterday), licensed MIT. It adds 131 tokens to every session and 5,601 once invoked, about $0.0007 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.
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…