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 skills/microsoft/power-platform-skills/add-data-sourcenpx skills add microsoft/power-platform-skills --skill add-data-sourcegit 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.00116 | $0.01006 |
| Opus 5 | $0.00058 | $0.00503 |
| Sonnet 5 | $0.00023 | $0.00201 |
| Haiku 4.5 | $0.00012 | $0.00101 |
Grade A, and why
add-data-source 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data sources, connections, and API connectors cannot be added by the coding agent — they must be added through the Power Apps Studio interface. This skill informs the user, guides them to add the connection in their Studio session, verifies it is available via the MCP server, and then continues with any pending work.
Phase 0 — Identify the Connection Type
From the user's request, determine what they want to add and how to verify it:
| Request type | Verify with |
|---|---|
| Data source (SharePoint list, Dataverse table, SQL table, Excel file, OneDrive, etc.) | list_data_sources |
| API / connector (Office 365 Users, Teams, custom connector, etc.) | list_apis |
| Unclear | Both list_data_sources and list_apis |
Note what the user is trying to add so you can look for it by name in Phase 3.
Phase 1 — Inform the User
Explain that this step requires action in their Studio session. Tell the user:
- The coding agent cannot add data sources or connections programmatically — this must be done directly in Power Apps Studio.
- To add the connection, follow these steps in their open Studio session:
- Open the Data panel in the left sidebar
- Click Add data
- Search for the data source or connector they want (e.g., "SharePoint", "Dataverse", "SQL Server", "Office 365 Users")
- Follow the authentication prompts and select the specific table, list, file, or dataset
- Once added, the connection will be available to the MCP server and you can continue.
Phase 2 — Wait for Confirmation
Use AskUserQuestion to pause until the user has completed the steps in Studio:
"Please add the data source or connection in your Power Apps Studio session. Reply here when it's ready and I'll verify the connection before continuing."
Do not proceed until the user confirms they have added it.
Phase 3 — Verify the Connection
Once the user confirms, call the appropriate MCP tools to check that the connection is now available:
- If the request was for a data source: call
list_data_sources - If the request was for an API / connector: call
list_apis - If the type was unclear: call both in parallel
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 · 69 lines · 116 tokens per session scan A d2991a6e916d
add-data-source is a skill published in the GitHub repository microsoft/power-platform-skills (784 stars, last pushed 3d ago), licensed MIT. It adds 116 tokens to every session and 1,006 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-08-30.
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.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
audit-reproducibility
Enforce the replication-protocol.md rule by cross-checking numeric claims in a manuscript against the actual R / Stata / Python outputs. Report PASS/FAIL per claim against tolerance thresholds. Use before submission and before releasing a replication package.
research-report
Summarize deep research results into markdown report, cover all fields, skip uncertain values.