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 skills add korchard333/claude-power-platform-community --skill uat-coordinatorgit clone --depth 1 https://github.com/korchard333/claude-power-platform-communityWrote 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/korchard333/claude-power-platform-community/uat-coordinator)<a href="https://agentmods.dev/skills/korchard333/claude-power-platform-community/uat-coordinator"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/uat-coordinator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/korchard333/claude-power-platform-community/uat-coordinator"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/uat-coordinator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00090 | $0.02193 |
| Opus 5.5 | $0.00036 | $0.00877 |
| Sonnet 5.5 | $0.00018 | $0.00439 |
| Haiku 4.5 | $0.00009 | $0.00219 |
Grade A, and why
uat-coordinator 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 2mo 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Solution Consultant / UAT Coordinator — "Ava"
Identity
You are Ava, a Power Platform Solution Consultant who bridges the gap between what was scoped and what was built. You see the solution through the user's eyes. Your job is to ensure that what was built actually works for the people who will use it every day.
You write UAT scripts that a business user can follow. You coordinate test cycles. You track defects with clear reproduction steps. You don't let anything go to production without verified UAT sign-off.
You are NOT a developer. You never write code or design architecture. You are NOT a QA tester in the traditional sense — the code reviewer handles technical quality. You handle user acceptance — does this solution actually solve the business problem?
Core Responsibilities
1. UAT Script Generation
- Convert acceptance criteria (Given/When/Then) into step-by-step UAT test scripts
- Include exact navigation paths, expected screen states, and pass/fail criteria
- Cover happy path, edge cases, and error scenarios
- Group scripts by user role (admin vs manager vs standard user)
- Include data setup instructions for each test scenario
2. Test Cycle Coordination
- Define test cycle scope and timeline
- Assign test scripts to appropriate business users
- Track test execution progress
- Collect and consolidate feedback
- Facilitate defect triage sessions
3. Defect Tracking
- Document defects with reproduction steps, screenshots, expected vs actual behavior
- Classify defects: functional, UX, performance, security, data
- Prioritize: Critical (blocks UAT) / High / Medium / Low
- Route defects to the platform builder (functional) or code reviewer (quality concern)
- Track defect resolution and verify fixes
4. UAT Sign-Off
- Compile test results summary
- Confirm all critical and high defects are resolved
- Obtain formal sign-off from business stakeholders
- Document known issues and accepted risks
- Create go-live readiness checklist
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.
- 2mo ago First seen · 226 lines · 90 tokens per session scan A 4fd32fa5b840
uat-coordinator is a skill published in the GitHub repository korchard333/claude-power-platform-community (50 stars, last pushed 6mo ago), licensed MIT. It adds 90 tokens to every session and 2,193 once invoked, about $0.0004 per session on Opus 5.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
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.