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 FortiumPartners/ensemble --skill ensemble-playwright-testgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/ensemble-playwright-test)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-playwright-test"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-playwright-test.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.00031 | $0.00348 |
| Opus 5 | $0.00015 | $0.00174 |
| Sonnet 5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
ensemble-playwright-test 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.
What it actually says
Ensemble Command: /ensemble:playwright-test
This Codex skill mirrors the Ensemble slash command /ensemble:playwright-test.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Automated application testing and error resolution using Playwright MCP server integration. Generates test specs, executes tests, captures failures, and provides debugging context for quick resolution.
Workflow
Phase 1: Test Planning
1. User Flow Identification Identify critical user flows to test
2. Test Spec Generation Generate Playwright test specifications
Phase 2: Test Execution
1. Test Run Execute Playwright tests with trace capture
Delegation: @playwright-tester Test specifications and target application URL
2. Result Analysis Analyze test results and capture failures
Phase 3: Error Resolution
1. Failure Diagnosis Analyze failure screenshots and traces
2. Fix Implementation Implement fixes for identified issues
Expected Output
Format: Test Results and Traces
Structure:
- Test Report: Pass/fail status for all tests
- Traces: Playwright traces for failed tests
- Screenshots: Failure screenshots for debugging
Usage
/ensemble:playwright-test
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 · 63 lines · 31 tokens per session scan A 36dc41901b51
ensemble-playwright-test is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 348 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-30.
Other skills, from other repositories
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
playwright-cli
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.
agent-browser
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.
BrowserBash Browser Automation
BrowserBash is a vendor-independent, natural-language browser automation CLI. Drive a real browser from plain-English objectives or committable Markdown tests, run on local Chrome, CDP/Playwright MCP, Browserbase, LambdaTest, or BrowserStack, and stream NDJSON results with CI exit codes — using free local Ollama…
e2e
Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".
test-app
Verify a running Mendix app in a browser with Playwright, with OQL for data assertions. Use when asked to test or validate the app end to end, or to confirm that generated pages actually render.