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/verifynpx skills add joshsmithxrm/power-platform-developer-suite --skill verifygit 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/verify)<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/verify"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/verify.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.00035 | $0.01019 |
| Opus 5 | $0.00017 | $0.00509 |
| Sonnet 5 | $0.00007 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
verify 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify
AI self-verification of implemented work. Goes beyond unit tests to verify code actually works in its runtime environment.
Usage
/verify- auto-detect from recent changes/verify cli|tui|extension|mcp|workflow- explicit mode
Prerequisites
| Mode | Required |
|---|---|
| cli | Bash tool only |
| tui | tests/PPDS.Tui.E2eTests/tools/tui-verify.mjs (@microsoft/tui-test, node-pty) |
| extension | src/PPDS.Extension/tools/webview-cdp.mjs (@playwright/test, @vscode/test-electron) |
| mcp | npx @modelcontextprotocol/inspector |
If a prerequisite is missing, tell the user what to install and stop.
Process
1. Detect component
From $ARGUMENTS or recent changes:
src/PPDS.Cli/Commands/->cli, src/PPDS.Cli/Tui/->tui,
src/PPDS.Extension/->extension, src/PPDS.Mcp/->mcp,
.claude/+scripts/->workflow. No match: ask.
2. Unit tests first
- CLI/TUI:
dotnet test PPDS.sln --filter "Category!=Integration" -v q - Extension:
npm run test --prefix src/PPDS.Extension - MCP:
dotnet test --filter "FullyQualifiedName~Mcp" -v q
Don't waste interactive cycles on broken code.
3. CLI mode
dotnet build src/PPDS.Cli/PPDS.Cli.csproj -f net10.0
.\src\PPDS.Cli\bin\Debug\net10.0\ppds.exe <command> <args>
Verify exit 0, format correct, edge cases (empty/invalid/no-auth).
4. TUI mode
See REFERENCE.md "TUI Mode - worked example" for the Phase A/B/C
commands. Phase B is mandatory when changed files touch
src/PPDS.Cli/Tui/.
5. Extension mode
See REFERENCE.md "Extension Mode - worked example" for Phase A/B/C
commands. Phase B is mandatory when query/data/panel files change.
6. MCP mode
npx @modelcontextprotocol/inspector --cli --server "ppds-mcp-server"
Per tool: valid->success shape; edge case->error handling; matches schema.
7. Workflow mode
Check 1 - Python tests (the full automation suite — hook behavior, skill content, bash portability):
python -m pytest tests/ scripts/ --import-mode=importlib -q
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.
- 4d ago First seen · 111 lines · 35 tokens per session scan A d85da3ac0b84
verify is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (5 stars, last pushed 11d ago), licensed MIT. It adds 35 tokens to every session and 1,019 once invoked, about $0.0002 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
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…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…