Borrowing it
Nothing to install: this file belongs to gurvinder-dhillon/powerbi-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gurvinder-dhillon/powerbi-mcp/main/.claude/skills/powerbi-mcp-server-tester/SKILL.mdgit clone --depth 1 https://github.com/gurvinder-dhillon/powerbi-mcpWrote 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/gurvinder-dhillon/powerbi-mcp/powerbi-mcp-server-tester)<a href="https://agentmods.dev/skills/gurvinder-dhillon/powerbi-mcp/powerbi-mcp-server-tester"><img src="https://agentmods.dev/badge/skills/gurvinder-dhillon/powerbi-mcp/powerbi-mcp-server-tester/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/gurvinder-dhillon/powerbi-mcp/powerbi-mcp-server-tester"><img src="https://agentmods.dev/badge/skills/gurvinder-dhillon/powerbi-mcp/powerbi-mcp-server-tester.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.00102 | $0.01514 |
| Opus 5.5 | $0.00041 | $0.00606 |
| Sonnet 5.5 | $0.00020 | $0.00303 |
| Haiku 4.5 | $0.00010 | $0.00151 |
Grade A, and why
powerbi-mcp-server-tester 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 1mo 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerBI MCP Server Tester
Automated testing framework for the PowerBI MCP server that validates functionality, Azure AD authentication, and PowerBI tool implementations using MCP Inspector and Playwright automation.
Prerequisites
Before testing, ensure:
-
Environment Variables: PowerBI credentials must be set in
.envfilePOWERBI_TENANT_ID- Azure AD tenant IDPOWERBI_CLIENT_ID- Application (client) IDPOWERBI_CLIENT_SECRET- Client secret value
-
MCP Inspector: Installed globally via npx (no manual installation needed)
-
Playwright MCP: Must be enabled as an MCP server
-
PowerBI MCP Server: Must be in the powerbi-mcp project directory with server code in
src/
Testing Workflow
Step 1: Verify Prerequisites
Ask the user to confirm:
- "Please confirm your PowerBI environment variables (POWERBI_TENANT_ID, POWERBI_CLIENT_ID, POWERBI_CLIENT_SECRET) are set in your
.envfile" - "Should I test all PowerBI tools or focus on specific ones (workspaces, datasets, queries)?"
Step 2: Launch MCP Inspector
Start the MCP Inspector with the PowerBI MCP server (assumes you're in the powerbi-mcp directory):
# Background task - don't block on this
npx @modelcontextprotocol/inspector uv run run-server
Wait 5-10 seconds for Inspector to start, then read the output to get the Inspector URL.
Step 3: Automated Testing with Playwright
Use Playwright MCP to:
-
Navigate to Inspector
- Open the Inspector URL from the background task output
-
Verify Connection
- Click "Connect" button
- Wait for "Connected" status
- Verify server name and version appear
-
List Available Tools
- Click "List Tools" button
- Count and record all available tools
- Identify which tools are read-only (GET/list/read operations)
-
Test Each Read-Only Tool For each read-only tool:
- Click on the tool to view its details
- Review parameters and their types
- If the tool has optional parameters, test with defaults first
- If the tool has required parameters, use sample values or ask user for test values
- Click "Run Tool" button
- Wait for result (success or error)
- Record the outcome
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.
- 1mo ago First seen · 206 lines · 102 tokens per session scan A 6c5d097fec41
powerbi-mcp-server-tester is a skill published in the GitHub repository gurvinder-dhillon/powerbi-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 102 tokens to every session and 1,514 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-31.
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.
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.