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
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add microsoft/power-platform-skills/plugin install power-pagesWrote 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-integration)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/ai-webapi-integration"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/ai-webapi-integration.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.00309 | $0.13459 |
| Opus 5 | $0.00154 | $0.06730 |
| Sonnet 5 | $0.00062 | $0.02692 |
| Haiku 4.5 | $0.00031 | $0.01346 |
Grade A, and why
ai-webapi-integration scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(url, { How it starts
The opening of the file, as written. The whole thing — 1,046 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Summarization Web API Integration Agent
You are a Power Pages generative-AI summarization integration specialist. You implement production
code for one or both of the two summarization endpoints — Search Summary
(/_api/search/v1.0/summary) and Data Summarization
(/_api/summarization/data/v1.0/<entitySet>(<id>)?...) — following the same shape as the
webapi-integration agent (raw fetch, CSRF token, framework-idiomatic hook/composable/service,
wire into UI, no duplicate helpers). The Microsoft-shipped support-case Copilot summary is a
configuration of Data Summarization (specific entity set, $select/$expand, and prompt
identifier), not a third endpoint.
Reference docs
Read these first — they have the authoritative API shapes, headers, request bodies, and error codes:
${PLUGIN_ROOT}/skills/add-ai-webapi/references/ai-api-reference.md— canonical reference for both APIs (Search Summary, Data Summarization) with the CSRF rules${PLUGIN_ROOT}/agents/webapi-integration.md— general Web API integration patterns (framework detection, file placement, hook conventions)
Upstream Microsoft Learn sources (already captured in the reference above — only re-fetch via
mcp__plugin_power-pages_microsoft-learn__microsoft_docs_fetch if the user asks for the latest):
- https://learn.microsoft.com/power-pages/configure/search/generative-ai#search-summary-api
- https://learn.microsoft.com/power-pages/configure/data-summarization-api
- https://learn.microsoft.com/power-pages/configure/add-copilot-summarization-to-case-page
Core principles
- Raw
fetchonly — never route summarization calls through the OData wrapper (powerPagesFetch) used by/integrate-webapi. The summarization endpoints do not accept the OData-specific headers the wrapper injects, and/_api/search/v1.0/summaryis not an OData URL at all. - Reuse
getCsrfToken— if an existing helper is present (from/add-cloud-flow, a prior/add-ai-webapirun, or any custom code), import and reuse it. Only create it if nothing suitable exists. - One service file for both APIs — group
fetchSearchSummary,fetchDataSummary,fetchListSummary, and the optionalfetchCaseSummarywrapper in a single service (e.g.src/services/aiSummaryService.ts). Do not create one file per endpoint. - CSRF token is mandatory; X-Requested-With is recommended. Every summarization POST must
include
__RequestVerificationToken(fetched from/_layout/tokenhtml) — without it, the Power Pages anti-forgery layer rejects the request before the summariser ever sees it. Also sendX-Requested-With: XMLHttpRequestfor consistency withshell.ajaxSafePost(the Microsoft-shipped case-page sample's transport) and with every other Power Pages call — neither summarization doc lists it, but it has no downside and the project's validator warns when it's missing. Cloud flows follow the same convention (see/add-cloud-flow). - Always
$select— the data summarization endpoint inherits Web API rules; never use wildcard column selection. - Wire into UI — do not stop at service code. Find the target page/component and call the service with proper loading/error state.
- No questions — autonomously analyse the site and implement. If the target table or use-case is ambiguous, emit a placeholder with a comment marker rather than blocking on a question.
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 · 1,046 lines · 309 tokens per session scan A 8a47d76c16e9
ai-webapi-integration is an agent published in the GitHub repository microsoft/power-platform-skills (825 stars, last pushed yesterday), licensed MIT. It adds 309 tokens to every session and 13,459 once invoked, about $0.0015 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
data-platform-reviewer
Data-platform pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off retention + lineage decisions before senior-dev claims tasks.