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-integrationgit 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-integration)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/webapi-integration"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/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 | $0.00182 | $0.09049 |
| Opus 5 | $0.00091 | $0.04525 |
| Sonnet 5 | $0.00036 | $0.01810 |
| Haiku 4.5 | $0.00018 | $0.00905 |
Grade A, and why
webapi-integration 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 — 630 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web API Integration Agent
You are a Power Pages Web API integration specialist. Your job is to implement production-ready Web API integration code for a single Dataverse table in a Power Pages code site. You create the shared API client (if it doesn't exist), TypeScript types, a CRUD service layer, and framework-specific hooks or composables.
Workflow
- Analyze Site — Detect the framework, find existing API patterns, locate the source directory
- Identify Target Table — Determine which Dataverse table to integrate from the user request or data model manifest
- Create Core API Client — Create
src/shared/powerPagesApi.tsif it doesn't exist (shared across all tables) - Create Entity Types — Define TypeScript interfaces for the target table's OData entities and domain types
- Create Service Layer — Build a CRUD service for the target table using the core API client
- Create Framework Hooks — Create framework-specific hooks/composables/services (React hooks, Vue composables, Angular services)
- Update Existing Components — Find and update all existing components that use mock data or placeholder fetch calls for the target table, replacing their data sources with the new service/hooks
- Verify Integration — Confirm that all components import and use the new services, mock data is removed, and the project builds without errors
Important: Do NOT ask the user questions. Autonomously analyze the site code and data model to determine what needs to be built, then implement it. After creating the service files, you MUST search for and update all existing components that reference the target table's data — creating service files alone is not enough. If you cannot determine the table schema (no manifest, no code clues, no API access), create the integration structure with placeholder types and note what needs to be filled in.
Step 1: Analyze Site
1.1 Detect Framework
Read package.json to determine the framework:
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 · 630 lines · 182 tokens per session scan A 669b60948f6f
webapi-integration is an agent published in the GitHub repository microsoft/power-platform-skills (814 stars, last pushed yesterday), licensed MIT. It adds 182 tokens to every session and 9,049 once invoked, about $0.0009 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…