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 testinggit 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/testing)<a href="https://agentmods.dev/skills/korchard333/claude-power-platform-community/testing"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/testing.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.1 | $0.00054 | $0.00895 |
| Opus 5 | $0.00027 | $0.00447 |
| Sonnet 5 | $0.00011 | $0.00179 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
testing 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 8d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Power Platform Testing Strategy
When to Use
Trigger when designing test plans, automating tests, debugging production issues, or validating deployments for any Power Platform solution — Code Apps, Canvas Apps, Model-Driven Apps, Flows, Plugins, or Portals.
Testing Pyramid for Power Platform
└──-------------------+
| E2E / UI Tests | <-- Slowest, most brittle
| (Playwright, ERP) |
└──-------------------+
| Integration Tests | <-- Validate cross-component
| (Solution Check) |
└──-------------------+
| Unit Tests | <-- Fastest, most reliable
| (xUnit, Jest, PTS) |
└──-------------------+
Testing by Component Type
| Component | Unit Test Tool | Integration Test | E2E Test |
|---|---|---|---|
| Code App (React) | Vitest/Jest + RTL | Playwright | Playwright |
| Canvas App | — | Power Apps Test Studio | Power Apps Test Studio |
| Model-Driven App | — | — | EasyRepro / Playwright |
| Plugin (C#) | xUnit + FakeXrmEasy | Plugin Trace Log | — |
| Power Automate Flow | — | Flow Checker + manual | Flow run history |
| PCF Control | Jest | PCF test harness | Playwright |
| Custom Connector | Postman / REST tests | Connector test tab | Flow integration test |
| Desktop Flow (RPA) | Subflow test suite (Wave 1 2026) | Flow run history | Screenshot capture on failure |
| Power Pages | — | — | Playwright / Selenium |
⚠️ REQUIRED: Load Sub-Files Before Implementation
SKILL.md is a summary only — it is NOT sufficient for implementation.
The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:
- Code App Testing — Vitest/Jest + React Testing Library, component tests, hook tests, E2E with Playwright
- Canvas App Testing — Power Apps Test Studio, Flow testing, Monitor tool, EasyRepro for Model-Driven Apps
- Plugin Testing — xUnit + FakeXrmEasy setup, mocking IOrganizationService, testing plugin execution
- Accessibility Testing — axe-core + Playwright, manual checklist, Canvas App accessibility checker
- CI/CD Integration — Solution Checker (static analysis), GitHub Actions, test data management, deployment validation smoke tests
What ships with it
5 files 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.
- 8d ago First seen · 81 lines · 54 tokens per session scan A f1b3fb88f5ce
testing is a skill published in the GitHub repository korchard333/claude-power-platform-community (46 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 895 once invoked, about $0.0003 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-30.
Other skills, from other repositories
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
prd-auto-test-loop
A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.
test-automation-expert
Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…