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 instructions/microsoft/power-platform-skills/agents-mdgit 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/instructions/microsoft/power-platform-skills/agents-md)<a href="https://agentmods.dev/instructions/microsoft/power-platform-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/microsoft/power-platform-skills/agents-md.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 | $0.04726 | $0.04726 |
| Opus 5 | $0.02363 | $0.02363 |
| Sonnet 5 | $0.00945 | $0.00945 |
| Haiku 4.5 | $0.00473 | $0.00473 |
Grade A, and why
power-platform-skills AGENTS.md 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 4d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power Platform Skills - Development Guidelines
This file provides guidance to AI Agents when working with code in this repository.
What This Repo Is
A plugin marketplace for Power Platform development by Microsoft. The Open Plugins marketplace manifest (marketplace.json) references individual plugins in plugins/. Each plugin has its own AGENTS.md with plugin-specific guidance.
This Repo Is PUBLIC — keep internal detail out of it
Everything here — code, docs, commit messages, PR descriptions, and branch names — is world-readable. Write for a reader outside Microsoft who cannot see any internal system.
Do not commit:
- Internal hosts, repos or paths —
*.ghe.comlinks, internal repo names, or a path into an internal repo's doc tree. Naming one discloses its existence and its structure. - References to internal documents, including indexes into them — "spec rank 14", "Group N P1", "(resolves C2, I1)", "see the R1 review". A reader who cannot open the document gets nothing from the pointer, and it advertises the document.
- Real environment, tenant or org identifiers — Dataverse environment names/URLs, tenant GUIDs,
subscription ids. These name real infrastructure. In examples use an obvious placeholder
(
https://contoso.crm.dynamics.com,<envUrl>); to record that something was live-verified, keep the claim and drop the environment ("live-verified", not "live-verified on "). - Internal review process — who or which model reviewed something, how many rounds, internal finding ids. "Adversarially reviewed" is a useful signal; the rest is internal.
- Exploratory design docs for UNBUILT work — roadmaps, prioritisation, and candid notes on
limitations. A design doc for something that shipped is fine and often valuable (see
plugins/model-apps/docs/); a proposal for something that has not is internal. - Pointers to files that are not in the repo — a citation nobody can resolve is noise at best.
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.
- 4d ago First seen · 295 lines · 4,726 tokens per session scan A ac258120d752
power-platform-skills AGENTS.md is an instructions file published in the GitHub repository microsoft/power-platform-skills (814 stars, last pushed today), licensed MIT. It adds 4,726 tokens to every session, about $0.0236 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 instructions, from other repositories
recursive-decomposition-skill AGENTS.md
Instructions for massimodeluisa/recursive-decomposition-skill, covering agents: recursive-decomposition skill, read these first (mandatory), language policy, non-negotiables and commands.
the-foundry AGENTS.md
AGENTS.md instructions for attac-t/the-foundry, covering the foundry, doctrine and rules.
swarms CLAUDE.md
Instructions for DheerG/swarms, a project described as: Achieve extraordinary results with claude code across a variety of tasks.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.