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 skills add microsoft/power-platform-skills --skill add-localizationgit 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/skills/microsoft/power-platform-skills/add-localization)<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/add-localization"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/add-localization/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/skills/microsoft/power-platform-skills/add-localization"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/add-localization.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.00069 | $0.12504 |
| Opus 5.5 | $0.00028 | $0.05002 |
| Sonnet 5.5 | $0.00014 | $0.02501 |
| Haiku 4.5 | $0.00007 | $0.01250 |
Grade A, and why
add-localization 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 5d 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 — 1,180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin check: Run
node "${PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
Add Localization
Add framework-appropriate localization to a Power Pages code-site SPA. This skill changes only client-side site artifacts; it never enables Dataverse environment languages or translates Dataverse records.
Initial request: $ARGUMENTS
Read ${PLUGIN_ROOT}/references/i18n-frameworks.md and
${PLUGIN_ROOT}/references/bidirectional-design.md before planning or editing. Also apply
${PLUGIN_ROOT}/references/site-modification-integrity.md to all existing and future visible
site changes.
Core principles
- Detect framework and existing localization from project evidence.
- Read mode availability only from
localization-config.js; never plan or preserve a mode that is currently unavailable. - Preserve valid available package/mode choices, the default locale, and non-empty translations.
- Ask questions in the fixed order below; skip only documented conditional questions.
- Validate language tags and package alternatives with deterministic scripts.
- Require plan approval before package installation or project-file changes.
- Use agent-generated translation only during authoring; never add a deployed translation service or credentials.
- Always show: AI translations may contain errors - please verify them before publishing.
- Treat
[FROM_CREATE_SITE]in$ARGUMENTSas invocation context. It suppresses this skill's deploy prompt so create-site remains deployment owner. - Generate a locale coordinator only for React, Vue, and runtime Angular. Single-language and dormant static implementations do not receive it.
Workflow
- Detect project and existing localization.
- Gather and validate configuration.
- Render, open, and approve the implementation plan.
- Configure localization infrastructure.
- Extract and localize content.
- Verify localization independently.
- Review changes with the maker.
- Record usage and complete or offer deployment.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 1,180 lines · 69 tokens per session scan A c5b287b4ef82
add-localization is a skill published in the GitHub repository microsoft/power-platform-skills (1,005 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 12,504 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-10-10.
Other skills, from other repositories
canvas-apps-ui-gen
Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.
portable-text-serialization
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown…
ui-development
Build UI pages and extensions for Falcon Foundry apps using React or Vue with the Shoelace design system and Foundry-JS. TRIGGER when user asks to "create a UI page", "build a UI extension", "add a Shoelace component", "call an API from the UI", runs foundry ui pages create or foundry ui run, or needs help with Vite…
software-localisation
Implements production-grade i18n/l10n for React, Vue, Angular, and Next.js with ICU format and RTL support. Use when setting up or debugging localisation.
react-i18n
Use when implementing translations in a React app (not Next.js) with react-i18next — useTranslation, namespaces, pluralization, Suspense.
astro-integrations
Use when adding React, Vue, Svelte, Solid, Preact, or another UI framework to an Astro project via @astrojs/ integrations.