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/screen-plannergit clone --depth 1 https://github.com/microsoft/power-platform-skillsWhat 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.00071 | $0.17506 |
| Opus 5 | $0.00036 | $0.08753 |
| Sonnet 5 | $0.00014 | $0.03501 |
| Haiku 4.5 | $0.00007 | $0.01751 |
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 3d 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 — 774 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
npx power-apps *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.
- 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.
Inputs You Can Rely On
The planner gives you:
- App requirements (
$ARGUMENTS) - Target users + device class (phone/tablet, internal/external)
- Target platforms (iOS / Android)
- Aesthetic direction
- Features the user listed
phase— one ofgraph|specs| unset (back-compat = full run, equivalent tospecsafter an inline graph)
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.
- 3d 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 (784 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 17,506 once invoked, about $0.0004 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-08-30.
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…
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.
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.
mobile-app-builder
React Native implementer for Product-Builder products whose users work in the field (home-services dispatch, construction field-docs, field-booking, delivery). Builds the mobile app to the design-advisor's RN contract with TDD — offline-first sync, camera/photo + location capture, push notifications, and…