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 trebormc/drupal-ai-agents --skill playwright-testinggit clone --depth 1 https://github.com/trebormc/drupal-ai-agentsWrote 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/trebormc/drupal-ai-agents/playwright-testing)<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/playwright-testing"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/playwright-testing/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/trebormc/drupal-ai-agents/playwright-testing"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/playwright-testing.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.00154 | $0.02748 |
| Opus 5.5 | $0.00062 | $0.01099 |
| Sonnet 5.5 | $0.00031 | $0.00550 |
| Haiku 4.5 | $0.00015 | $0.00275 |
Grade A, and why
playwright-testing scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Never use curl for testing Drupal functionality. Use Playwright MCP instead. How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critical Rules
- NEVER use curl for testing Drupal pages — it cannot execute JS or simulate user navigation
- ALWAYS use HTTP (not HTTPS) for all Playwright navigation in DDEV — self-signed SSL certificates cause failures
- Convert ALL URLs from
https://tohttp://before passing tobrowser_navigate, including drush uli output - NEVER create JavaScript files, Node.js scripts, or Playwright test scripts to interact with the browser. Always use the Playwright MCP tools directly. If MCP fails, troubleshoot the connection — do NOT generate script files as a workaround
MCP Connection
Playwright MCP tools (browser_navigate, browser_take_screenshot, etc.) are registered as native tools via the MCP server configuration. They should be available directly — no manual HTTP/SSE protocol is needed.
- MCP URL:
http://playwright-mcp:8931/mcp(or$PLAYWRIGHT_MCP_URL) - Site URL: use
$DDEV_HTTP_URL(already HTTP).$DDEV_PRIMARY_URLis HTTPS — if you use it, convert to HTTP first - Web Container: accessible via
ssh web(for commands likedrush uli)
If MCP tools are not available
This is a RECOVERY procedure only. If the browser_ tools are visible, skip this entire section.*
If the browser tools are not showing up as available tools:
# 1. Check if Playwright MCP is responding (works without Docker socket)
curl -s --max-time 3 http://playwright-mcp:8931/sse \
-H "Accept: text/event-stream" | head -1
# Success: "event: endpoint"
# Failure: connection refused → container not running
# 2. Verify environment variable
echo $PLAYWRIGHT_MCP_URL
# Should return: http://playwright-mcp:8931/mcp
# 3. Restart DDEV to recover the container
# (tell the user to run: ddev restart)
NEVER work around a failed MCP connection by writing .js or .mjs files.
Environment Architecture
┌─────────────────────────────────────────────────────────────┐
│ AI Container (OpenCode or Claude Code) │
│ - Runs agents, reads files, executes bash │
│ - Connects to Web via: ssh web │
│ - Uses Playwright via: MCP tools (native) │
└──────────────┬──────────────────────┬───────────────────────┘
│ SSH │ MCP protocol
▼ ▼
┌──────────────────────────┐ ┌───────────────────────────────┐
│ Web Container │ │ Playwright MCP Container │
│ (ddev-{project}-web) │ │ (ddev-{project}-playwright- │
│ - PHP, Drupal, Drush │ │ mcp) │
│ - npm, Composer │ │ - Chromium browser │
└──────────────────────────┘ │ - MCP tools on port 8931 │
│ - Navigates to Web Container │
└───────────────────────────────┘
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 · 249 lines · 154 tokens per session scan A 9dd68fbfc712
playwright-testing is a skill published in the GitHub repository trebormc/drupal-ai-agents (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 154 tokens to every session and 2,748 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
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.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…