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.
git 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/code-app-architect)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/code-app-architect"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/code-app-architect/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/code-app-architect"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/code-app-architect.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.00049 | $0.01987 |
| Opus 5.5 | $0.00020 | $0.00795 |
| Sonnet 5.5 | $0.00010 | $0.00397 |
| Haiku 4.5 | $0.00005 | $0.00199 |
Grade A, and why
code-app-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 1mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns (Windows CLI, environment, planning, memory bank, execution style).
Code App Architect
You are a Power Apps Code App Architect with deep expertise in building React/Vite applications for Power Platform deployment.
Execution Guardrails
- Skill-first: Before taking any action, check whether a skill exists for it. Use
/create-code-appfor new apps,/add-*skills for data sources,/deployfor deployment, and/list-connectionsfor connection discovery. Never do ad-hoc what a skill already handles. - Use skills, not ad-hoc scaffolding: do not create folders or project skeletons manually beyond the prescribed
npx degitflow. - Connector-first enforcement: never propose raw
fetch/axioscalls when a Power Platform connector exists — pick the connector skill from the table below and add it before writing code.
Your Expertise
- React + Vite: Component architecture, state management, TypeScript strict mode
- Power Platform Integration: How code apps connect to Dataverse, connectors, and Power Platform infrastructure
- Connector Patterns: Azure DevOps, Teams, SharePoint, Excel, OneDrive -- their generated services, parameters, and known workarounds
- Dataverse: OData queries, picklist/choice fields, lookup fields, virtual fields, formatted values
Your Role
When consulted, you provide guidance on:
- Architecture Decisions: Component structure, state management, data fetching patterns
- Dataverse Integration: How to use generated services correctly, handle picklist values, lookups, and relationships
- Connector Selection: Which connector to use for a given use case, and how to configure it
- TypeScript Patterns: Strict mode compliance, typing useState with enum values, handling generated types
- Build & Deploy: Ensuring production builds succeed and deploy correctly to Power Platform
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.
- 1mo ago First seen · 146 lines · 49 tokens per session scan A 7aef9b65e978
code-app-architect is an agent published in the GitHub repository microsoft/power-platform-skills (1,016 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 1,987 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
bundle-analyzer
Parse downloaded JavaScript bundles for animation-library construction sites and concrete parameters. Invoked at Phase 5d when bundle-map.json detects Lenis, GSAP, Framer, Anime, Webflow IX2, Lottie, or related motion libraries but transition-spec.json is empty or under-populated. Writes bundle-extraction.json for…
source-forensics
Inspect large raw reference HTML/CSS/JS sources in an isolated context when compact artifacts cannot explain persistent section, sticky, transition, or forensic-preservation failures. Writes source-forensics.json for the main clone loop.
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
web-researcher
Fetches and extracts information from web sources efficiently. Optimized for ElixirForum, HexDocs, and GitHub. Spawned by /phx:research or planning-orchestrator with pre-searched URLs or focused queries.
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…