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/qanpx skills add joshsmithxrm/power-platform-developer-suite --skill qagit 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/qa)<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/qa"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/qa.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.00044 | $0.04472 |
| Opus 5 | $0.00022 | $0.02236 |
| Sonnet 5 | $0.00009 | $0.00894 |
| Haiku 4.5 | $0.00004 | $0.00447 |
Grade A, and why
qa 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 — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA — Three-Agent Blind Verification
Dispatches three specialized agents with no source code access to verify quality from different angles: functional correctness, cross-panel consistency, and UX heuristics. Each agent interacts with the running product exactly as a user would.
Why three agents: A single verifier optimizes for its checklist and misses everything else. A functional tester won't notice inconsistent styling. A consistency auditor won't test button behavior. A UX evaluator won't verify sort order. Three lenses catch three categories of defects.
Usage
/qa — auto-detect from recent commits
/qa extension — verify extension changes via CDP
/qa cli — verify CLI changes by running commands
/qa mcp — verify MCP changes via Inspector
/qa "SELECT TOP 5 should return 5 rows" — explicit behavior description
Process
Step 1: Scope the Work
If $ARGUMENTS is a quoted description: Use it directly as the behavior to verify.
If $ARGUMENTS is a mode (extension/cli/mcp) or empty: Auto-generate from branch work:
# Ensure local main ref is current (worktrees can be stale)
git fetch origin main --quiet
# All commits on this feature branch
git log main..HEAD --format="%s%n%b" --no-merges
# All files changed on this branch
git diff main...HEAD --name-only
From the commits, extract observable behaviors:
feat(query): add X→ "X should be visible/functional in the UI"fix(ext): guard against Y→ "Y scenario should not crash"feat(extension): add Z to panel→ "Z should render in the panel"
From the changed files, identify which panels were modified — these are the panels that need exploratory inventory in Phase 1.
Be specific. Not "query works" — instead: "Execute SELECT TOP 5 name FROM account, verify exactly 5 rows in the results table."
Step 2: Detect Mode
From $ARGUMENTS or changed files:
src/PPDS.Extension/→ extension mode (CDP)src/PPDS.Cli/Commands/(not Serve/) → CLI mode (run commands)src/PPDS.Mcp/→ MCP mode (Inspector)src/PPDS.Cli/Tui/→ TUI mode (tui-verify)- Mixed → run applicable modes sequentially
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 · 453 lines · 44 tokens per session scan A 12ce4d3761b3
qa is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (5 stars, last pushed 11d ago), licensed MIT. It adds 44 tokens to every session and 4,472 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…
write-ui-tests
Creates UI tests for a GitHub issue and verifies they reproduce the bug. Iterates until tests actually fail (proving they catch the issue). Use when PR lacks tests or tests need to be created for an issue.
run-device-tests
Build and run .NET MAUI device tests locally with category filtering. Supports iOS, MacCatalyst, Android on macOS; Android, Windows on Windows. Use TestFilter to run specific test categories.
e2e
Run end-to-end Playwright tests via the developer CLI.
unity-playmode-recorded-playtest
Unity Editor を PlayMode 起動し、録画付きで end-to-end gameplay を検証する枠組み。第一選択はプレイテストDSL（Client.Playtest asmdef + 本スキル同梱の scripts/run-scenario.sh）による1コマンド一発実行で、preflight→PlayMode起動→シナリオ投入→result.json回収まで自動化される（実測ready26秒）。UI経路設置（ビルドメニュー→クリック/ドラッグ）とホットバー割当（建築ショートカット。歯車チェーンポール等）もDSLで操作可能。ユースケース別の詳細は references/…
editmode-in-playing-test
Skill "editmode-in-playing-test" from moorestech/moorestech, covering editmodeinplayingtest creator, 概要, 重要な前提, ワークフロー and 1. テストクラスを作成.