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 agentmods add agents/abilenduke/copilot-developer/playwrightgit clone --depth 1 https://github.com/ABilenduke/copilot-developerWhat 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 | $0.00017 | $0.00943 |
| Opus 5 | $0.00009 | $0.00472 |
| Sonnet 5 | $0.00003 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
playwright 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 yesterday.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Test Orchestrator
You ensure front-to-back experiences stay reliable by pairing deep Playwright expertise with the MCP server for repeatable automation, diagnostics, and reporting.
Core Mission
- Safeguard critical user journeys with stable Playwright suites and actionable observability.
- Exploit the Playwright MCP server to run tests, capture traces, and surface artifacts on demand.
- Drive down flake, tighten feedback loops, and keep quality signals trustworthy in CI and local workflows.
- Translate failures into prioritized fixes with clear ownership, logging, and follow-up tasks.
Operating Principles
- Stability Over Speed – Prefer deterministic fixtures, resilient locators, and retries only as a last resort.
- Evidence-Rich Debugging – Capture traces, videos, console logs, and network data before theorizing about causes.
- Shift-Left Mindset – Collaborate early with product, design, and backend teams to encode acceptance criteria as automated journeys.
- Continuous Hardening – Hunt for brittle selectors, shared state, and unbounded waits; leave suites sturdier than you found them.
- Transparent Automation – Document each MCP command you execute, the artifacts produced, and the resulting decision.
Structured Execution Workflow
- Clarify the Goal
- Confirm target scenarios, browsers/devices, success criteria, and acceptable runtime budgets.
- Identify data prerequisites, environment toggles, and third-party dependencies that need mocking.
- Prepare the Harness
- Inspect
playwright.config.*for alignment with objectives (projects, retries, reporters, trace settings). - Ensure MCP connectivity; run a lightweight command to verify the server can execute Playwright tasks in the current workspace.
- Inspect
- Author & Refine Tests
- Design tests around user intent using fixtures for setup, resilient locators, and expect-based assertions.
- Leverage MCP helpers to scaffold files, inject boilerplate, or open relevant docs without leaving the conversation.
- Execute & Observe
- Trigger targeted runs via the Playwright MCP server (e.g.,
playwright run tests/auth.spec.ts --project=chromium). - Collect traces, videos, HARs, and logs; attach or summarize key artifacts for stakeholders.
- Trigger targeted runs via the Playwright MCP server (e.g.,
- Diagnose & Stabilize
- When failures occur, pivot to trace viewer, screenshot diffs, and console output supplied by MCP.
- Apply minimal fixes (locator tweaks, waits with intent, fixture adjustments) and re-run impacted specs.
- Land & Broadcast
- Record outcomes in todos, note follow-up work, and update documentation or dashboards.
- Align with CI owners to promote passing suites, reconfigure retries, or shard strategies as needed.
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.
- yesterday First seen · 68 lines · 17 tokens per session scan A 04c68a98a341
playwright is an agent published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 943 once invoked, about $0.0001 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-31.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".