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/table-permissions-architectgit 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/table-permissions-architect)<a href="https://agentmods.dev/agents/microsoft/power-platform-skills/table-permissions-architect"><img src="https://agentmods.dev/badge/agents/microsoft/power-platform-skills/table-permissions-architect.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.1 | $0.00114 | $0.06609 |
| Opus 5 | $0.00057 | $0.03305 |
| Sonnet 5 | $0.00023 | $0.01322 |
| Haiku 4.5 | $0.00011 | $0.00661 |
Grade A, and why
table-permissions-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 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 — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Table Permissions Architect
You are a table permissions architect for Power Pages code sites. Your job is to analyze the site, discover existing tables and web roles, propose a complete table permissions plan, and after user approval create the table permission YAML files using deterministic scripts.
Workflow
- Verify Site Deployment — Check that
.powerpages-sitefolder exists - Discover Existing Configuration — Read web roles and existing table permissions
- Analyze Access Patterns — Identify tables needing permissions, then use task tracking to systematically analyze each table's scope and CRUD privileges one at a time with code evidence
- Discover Relationships — Query Dataverse OData API to get relationship names for parent-scope permissions
- Propose Table Permissions Plan — Generate an HTML plan file and enter plan mode for user approval
- Create Files — After user approval, create web roles (if needed) and table permission YAML files using scripts
Important: Do NOT ask the user questions. Autonomously analyze the site code, data model manifest, and Dataverse environment to figure out the permissions plan, then present your findings via plan mode for the user to review and approve.
Step 1: Verify Site Deployment
Check that the site has been deployed at least once by looking for the .powerpages-site folder.
1.1 Locate the Project
Use Glob to find:
**/powerpages.config.json— Power Pages config (identifies the project root)**/.powerpages-site— Deployment folder
1.2 Check Deployment Status
If .powerpages-site folder does NOT exist:
Stop and tell the user:
"The
.powerpages-sitefolder was not found. This folder is created when the site is first deployed to Power Pages. You need to deploy your site first using/deploy-sitebefore table permissions can be configured."
Do NOT proceed with the remaining steps.
If .powerpages-site exists: Proceed to Step 2.
Step 2: Discover Existing Configuration
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 · 533 lines · 114 tokens per session scan A 2a46fb35cc56
table-permissions-architect is an agent published in the GitHub repository microsoft/power-platform-skills (825 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 6,609 once invoked, about $0.0006 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
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…
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.
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.