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/joshsmithxrm/power-platform-developer-suite/setupnpx skills add joshsmithxrm/power-platform-developer-suite --skill setupgit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWhat 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.00003 | $0.02949 |
| Opus 5 | $0.00002 | $0.01474 |
| Sonnet 5 | $0.00001 | $0.00590 |
| Haiku 4.5 | $0.00000 | $0.00295 |
Grade B, and why
setup scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Add Stop hook to `~/.claude/settings.json`: How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup
Set up a complete PPDS development environment on a new machine, or refresh an existing one after pulling new code.
Usage
/setup - Interactive wizard (fresh machine or new contributor)
/setup --update - Non-interactive refresh (restore working build after code changes)
What It Does
Wizard mode (/setup): Prerequisites check → clone repos → install dependencies → build → install tools → check AI tooling → configure DX options → verify → summary.
Update mode (/setup --update): Prerequisites check → git pull → install dependencies → build → install tools → verify → summary. Zero questions asked.
Note: For terminal customization (Oh My Posh, eza, bat, etc.), see the separate dotfiles repo.
Process
Step 0: Platform Detection
Detect the platform to gate Windows-only steps:
uname -s
- Contains
MINGWorMSYS→ Windows (IS_WINDOWS=true) - Otherwise → Linux (
IS_WINDOWS=false)
Windows-only steps: VS Code check, extension VSIX install, sound notification.
Step 1: Prerequisites Check
Verify required tools are on PATH. If any are missing, print what's needed and stop — don't continue with a broken environment.
| Tool | Check | Min Version | Error |
|---|---|---|---|
| git | git --version |
Any | "git not found. Install from https://git-scm.com/" |
| node | node --version |
≥18 | "Node.js ≥18 required. Install from https://nodejs.org/" |
| dotnet | dotnet --version |
≥8.0 | ".NET SDK ≥8.0 required. Install from https://dot.net/" |
| pwsh | pwsh --version |
≥7.0 | "PowerShell 7+ required. Install from https://aka.ms/powershell" |
| code | code --version |
Any | "VS Code not found. VSIX installation will be skipped." |
Platform rules:
codecheck: Windows only. Skip entirely on Linux (not expected in dev containers).codeis a soft prerequisite: missingcodeprints a warning but does not stop setup.
Version parsing: node --version returns v18.19.0, dotnet --version returns 8.0.404. Parse the major version number for comparison.
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 · 350 lines · 3 tokens per session scan B d337050b7ec7
setup is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (5 stars, last pushed 9d ago), licensed MIT. It adds 3 tokens to every session and 2,949 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
PowerAppsControl
Drive the PowerAppsControl MCP server to UX-test a Power App end to end: open and verify an app URL, let the user choose a mode (smoke test = in-depth read-only exploration that produces a repeatable natural-language test plan; or run my test plan), then run it in a recorded session and produce a video + HTML report…
xrm-mcp
Skip steps you already have answers for. If you ran listtables or describetable earlier in the session, reuse those results.
review-test-failures
Classifies PR CI/test failures as likely PR-caused or unrelated, compares against base-branch baseline, and emits an overall merge-readiness verdict. Uses gathered GitHub/AzDO/Helix context and the shared MAUI CI facts.
pr-review
End-to-end PR reviewer for dotnet/maui. Orchestrates 3 phases — Pre-Flight, Try-Fix, Report. Gate runs separately before this skill. Use when asked to 'review PR #XXXXX', 'work on PR #XXXXX', or 'fix issue #XXXXX'.
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.