test-site

test-site is a skill for Claude Code from microsoft/power-platform-skills. It costs 46 tokens per session (10,564 once invoked), scanned A, original, MIT.

A browser-based test for a deployed Microsoft Power Pages website. It visits discoverable pages, checks API requests, and produces a report, including the actual response format returned by certain endpoints.

In plain words
What is it for?
Use it for runtime testing, link crawling, release smoke tests, API verification, and checking that frontend code reads API responses correctly.
Why use it?
It can reveal broken pages, failed API calls, or mismatches between what the site returns and what its frontend expects. It observes the live site without changing files or data.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; names the AskUserQuestion tool.

Part of the power-pages plugin — 29 skills, 5 agents shipped together

About the project

microsoft/power-platform-skills is a plugin marketplace containing reusable skills, agents, and commands for developing with Microsoft Power Platform. Developers use it to build and deploy Power Pages sites, model-driven Power Apps, and related solutions through Claude Code or GitHub Copilot. The catalogue entries are the marketplace's included skills, agents, plugins, and other agent components.

microsoft/power-platform-skills · 829 stars · on GitHub · aka.ms

Install

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.

agentmods
npx agentmods add skills/microsoft/power-platform-skills/test-site
Any agent
npx skills add microsoft/power-platform-skills --skill test-site
Clone the repo
git clone --depth 1 https://github.com/microsoft/power-platform-skills

Made for: Claude Code.

Or install power-pages, the plugin that ships this one along with the rest of its 29 skills, 5 agents.

Wrote 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.

agentmods badge for test-site

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/power-platform-skills/test-site.svg)](https://agentmods.dev/skills/microsoft/power-platform-skills/test-site)
Your own site
<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/test-site"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/test-site.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,564 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.10564
Opus 5 $0.00023 $0.05282
Sonnet 5 $0.00009 $0.02113
Haiku 4.5 $0.00005 $0.01056

Measured 2d ago against content hash 23ea6c6a288f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

test-site 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 2d 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.

plugins/power-pages/skills/test-site/SKILL.md · 805 lines

How it starts

The opening of the file, as written. The whole thing — 805 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plugin check: Run node "${PLUGIN_ROOT}/scripts/check-version.js" — if it outputs a message, show it to the user before proceeding.

Test Power Pages Site

Test a deployed, activated Power Pages site at runtime. Navigate the site in a browser, crawl all discoverable links, verify pages load correctly, capture network traffic to test API requests, and generate a comprehensive test report.

Prerequisite: This skill expects a deployed and activated Power Pages site. Run /deploy-site and /activate-site first if the site is not yet live.

Core Principles

  • Non-destructive: This skill is read-only — it does not create, modify, or delete any files or data. It only observes the site via the browser.
  • API-first testing: The primary goal beyond page loads is verifying that all /_api/ (Web API / OData) requests return successful responses.
  • Response-shape discovery: For /_api/serverlogics/ endpoints the test run must also capture and report the actual response body shape so frontend integrations can be written against the real response, not a guessed one. If frontend parsing or field access does not match the observed shape, report the mismatch and describe the parsing or field-access changes needed — this skill does not modify any code.
  • User-controlled authentication: Never attempt to log in automatically. Always ask the user to log in via the browser window when authentication is required.
  • Bounded crawling: Cap page crawling at 25 pages to prevent infinite loops on sites with dynamic or paginated URLs.

Validation Test Categories

Every run produces a categorized test report (docs/alm/last-test-site.json — see Phase 6.7a). Stable category IDs and the source phase that produces each:

Category id Display Name Source phase What it covers
site-load Site Load Phase 2 Homepage HTTP status, redirect handling, initial render. One card for the homepage; failures are critical.
authentication Authentication Phase 3 Anonymous-to-Entra redirect, private-site gate detection, login flow integrity. Critical for private sites.
page-crawl Page Crawl Phase 4 One card per page tested (up to 25). Each card carries the page URL, HTTP status, and any console errors. Severity scales with HTTP class (5xx → critical, 4xx on public → high).
web-api Web API Phase 5 One card per /_api/ endpoint observed during the run. Captures status code, response shape, and remediation hints (table-permissions / site-settings / inner-error settings).
auth-pages Authenticated Pages Phase 5.6 Pages that only became reachable after login. Skipped when the user opts out of authenticated testing.
auth-api Authenticated API Phase 5.6 API endpoints that only became callable after login. Skipped when authenticated testing is skipped.
console Console Health Aggregated Rolled-up count of console errors observed across all phases. Severity is medium by default.

Read the full file on GitHub · 805 lines

Changes

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.

  1. 2d ago First seen · 805 lines · 46 tokens per session scan A 23ea6c6a288f

Subscribe to this mod's changes

test-site is a skill published in the GitHub repository microsoft/power-platform-skills (829 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 10,564 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-09-03.

Related

Other skills, from other repositories

canvas-apps-ui-gen

Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.

ToluVictor/canvas-apps-tools · 71 tokens

browser-use

Drive a real browser to QA a running app. Screenshots, clicks, forms, evidence. Use when there is no Playwright suite, or when a human flow must be walked.

Kripu77/software-factory · 40 tokens

qa

Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).

SethGammon/Citadel · 56 tokens

browser-check

Drive a real browser and come back with a MEASUREMENT rather than an impression - console errors and >=400 responses as counts, computed styles as JSON when appearance is disputed. Use when work touches UI, when a review must verify one, or when fidelity-gate asks for its measurement.

jjanczur/tyran · 58 tokens

symfony:e2e-panther-playwright

Write end-to-end tests with Symfony Panther 2.4 for browser automation or Playwright for complex scenarios.

dev-toolings/superpowers-symfony · 31 tokens

agent-browser

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

tdimino/claude-code-minoan · 51 tokens