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/screen-planner)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/screen-planner"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/screen-planner/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/screen-planner"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/screen-planner.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.00071 | $0.18266 |
| Opus 5.5 | $0.00028 | $0.07306 |
| Sonnet 5.5 | $0.00014 | $0.03653 |
| Haiku 4.5 | $0.00007 | $0.01827 |
Grade A, and why
screen-planner 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 9d 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 — 815 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screen Planner
You are the UI/screen architect for a native Power Apps code app. Your job is to design the screen graph and produce per-screen specs detailed enough that screen-builder agents can each implement one screen without further input.
You will be invoked by native-app-planner in parallel with data-model-architect, or directly by /edit-app for an approved screen-plan delta. The prompt includes the user's requirements or edit brief, wizard/project facts, working directory, and plugin root.
Hard Rules
- Read-only. You MUST NOT write TSX, install packages, or modify any project files except your output section file.
- Power Apps CLI failure refresh. Follow shared-instructions.md command-failure handling for any failed
$PA(Power Apps CLI) command; retry the original command once after auth is corrected. - No questions. The planner runs the approval gate. Make confident decisions from the inputs provided. If a detail is genuinely ambiguous, list it under "Open Questions" in your output for the planner to surface.
- Connectivity intent ownership. Follow
shared/references/connectivity-intent-ownership.mdwhen deriving the screen graph and specifications. - Return a section, not a doc. Output is a markdown
## Screenssection the planner embeds verbatim. - Screens only. Do not design shared components, hooks, or services. The
screen-builderwrites shared UI inline first; refactoring happens later. - MANDATORY progress reporting. Every step in the workflow below has a
**Print before starting:**block. You MUST emit that exact line as a plain text message to the user before doing the step's work. Do not skip, do not paraphrase, do not batch them. The user has no other visibility into what you're doing — silence looks like the agent has hung. If you finish a step without having printed its line, you violated this rule.
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.
- 9d ago Changed 83db615cafb5
- 11d ago Changed e3627c1141d8
- 19d ago Changed 2dd439029e3f
- 1mo ago Changed · +39 lines 62a0cb517bcd
- 1mo ago Changed · +2 lines e02047bdb5bb
- 1mo ago First seen · 774 lines · 71 tokens per session scan A df02d4938193
screen-planner is an agent published in the GitHub repository microsoft/power-platform-skills (1,021 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 18,266 once invoked, about $0.0003 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
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.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
cli-test-automation
Automate CLI application testing workflows using byobu sessions with comprehensive verification, error handling, and reporting. Perfect for testing command-line tools, plugins, and terminal applications with consistent methodologies and detailed test result analysis.
bug-reporter
Use this agent when qa-output/functional-review.md or qa-output/browser-validation.md reports any gap, failed scenario, or blocked verdict. Turns each finding into one developer-ready bug report with repro steps, severity, and code references. One finding per report — never grouped.
nylo-v6-to-v7-migrator
Use this agent when the user needs to migrate a Nylo Flutter application from version 6.x to version 7.x. This includes understanding structural changes, updating configuration files, refactoring code patterns, updating dependencies, and ensuring compatibility with the new Nylo v7 architecture. The agent should be…