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/gatesnpx skills add joshsmithxrm/power-platform-developer-suite --skill gatesgit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWrote 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/joshsmithxrm/power-platform-developer-suite/gates)<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/gates"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/gates.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.00005 | $0.01134 |
| Opus 5 | $0.00003 | $0.00567 |
| Sonnet 5 | $0.00001 | $0.00227 |
| Haiku 4.5 | $0.00001 | $0.00113 |
Grade A, and why
gates 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gates
Mechanical pass/fail checks. No judgment, no opinions - compiler, linter, and tests either pass or they don't. Run before code reviews, after fix batches, and before PRs.
Read REFERENCE.md §1 "Why mechanical gates" for rationale.
Input
$ARGUMENTS = optional scope hint (extension for TS-only, dotnet for C#-only). Default: all applicable gates.
Process
Step 1: Detect What Changed
git diff --name-only main...HEAD
Categorize: .cs -> .NET gates; .ts/.js -> TypeScript gates; both -> all. If $ARGUMENTS specifies a scope, use that.
Step 1.5: Preflight Toolchain & Output Discipline
Before running any gate, confirm its toolchain is on PATH. A missing toolchain is a FAIL, never a SKIP - never report a TS gate as PASS or SKIP when npm is missing.
command -v dotnet >/dev/null 2>&1 || { echo "FAIL (preflight): dotnet missing"; exit 1; } # if .NET gates scheduled
command -v npm >/dev/null 2>&1 || {
command -v fnm >/dev/null 2>&1 && eval "$(fnm env --shell bash)" || true
command -v npm >/dev/null 2>&1 && echo "preflight: self-healed via fnm activation" \
|| { echo "FAIL (preflight): npm missing"; exit 1; }
} # if TS gates scheduled
Never pipe gate commands through tail/head/grep without set -o pipefail. The trailing command's exit code masks the real one. Read REFERENCE.md §8 "Preflight + pipefail" for safe truncation patterns.
Step 2: Run Gates
Gate 1: .NET Build (if C# changed)
dotnet build PPDS.sln -v q
Pass: 0 errors. On "used by another process", Read REFERENCE.md §2 "File-locking recovery".
Gate 2: .NET Tests (if C# changed)
dotnet test PPDS.sln --filter "Category!=Integration" -v q --no-build
Pass: 0 failures. Fail: report failing test names and assertion messages.
Gate 3: TypeScript Build (if TS/JS changed)
npm run compile --prefix src/PPDS.Extension
Pass: 0 errors.
Gate 3.5: TypeScript Type Check (if TS/JS changed)
npm run typecheck:all --prefix src/PPDS.Extension
Pass: 0 errors across host and webview tsconfigs. Read REFERENCE.md §3 "Compile vs typecheck" for why this is separate.
What ships with it
1 file 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 · 120 lines · 5 tokens per session scan A ad8a549a99b8
gates is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (5 stars, last pushed 11d ago), licensed MIT. It adds 5 tokens to every session and 1,134 once invoked, about $0.0000 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-31.
Other skills, from other repositories
dynamics365-expert
Expert in Dynamics 365 platform, model-driven apps, canvas apps, Power Automate flows, Dataverse, plugins, and custom workflows. Use when the user mentions Microsoft platforms, ERP, CRM, business apps, the Power Platform, or Dataverse, or when the task involves Dynamics 365 Applications, Dataverse Platform…
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.
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.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…