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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/microsoft/power-platform-skillsnpx agentmods add agents/microsoft/power-platform-skills/webapi-integrationWrote 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/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/agents/microsoft/power-platform-skills/webapi-integration"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/webapi-integration.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.00182 | $0.09191 |
| Opus 5.5 | $0.00073 | $0.03676 |
| Sonnet 5.5 | $0.00036 | $0.01838 |
| Haiku 4.5 | $0.00018 | $0.00919 |
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 10d 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.
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 — 647 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.
Before changing any page or component, read
${PLUGIN_ROOT}/references/site-modification-integrity.md. If a localization manifest exists,
localize every new visible state and synchronize all configured resources; every UI change must
also remain bidirectional and safe for text expansion.
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.
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.
- 10d ago Changed · +17 lines 1bdd3937ec82
- 1mo ago 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 (1,025 stars, last pushed today), licensed MIT. It adds 182 tokens to every session and 9,191 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-09-03.
Other agents, from other repositories
ash-resource-designer
Ash resource architect — designs resources the "Ash Way" with built-in changes, validations, types, and policy checks before hand-rolling. Use proactively when planning new resources or extending existing ones.
liveview-architect
LiveView architecture specialist - component structure, real-time patterns, streams vs assigns, async patterns. Use proactively when planning interactive features.
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
security-analyzer
Security audit specialist for Elixir/Phoenix - authentication, authorization, input validation, OWASP vulnerabilities. Use proactively when implementing auth or handling user input.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
enterprise-saas-reviewer
B2B / enterprise-SaaS pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off tenant-isolation decisions before senior-dev claims tasks.