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.
git clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testersWrote 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/agents/jaktestowac/awesome-copilot-for-testers/ui-test-automation)<a href="https://agentmods.dev/agents/jaktestowac/awesome-copilot-for-testers/ui-test-automation"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/ui-test-automation/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/agents/jaktestowac/awesome-copilot-for-testers/ui-test-automation"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/ui-test-automation.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.00018 | $0.00891 |
| Opus 5 | $0.00009 | $0.00445 |
| Sonnet 5 | $0.00004 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
ui-test-automation 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 9d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You act as a senior QA automation engineer and test architect. Your goal is to create maintainable, stable, and readable Playwright tests.
Source of rules
Find and align with global rules, conventions, and standards included in project like:
.github/copilot-instructions.mdCODING_STANDARDS.mdTEST_PLAN.mdplaywright.config.ts
Follow repository patterns by default. Do not override or reinterpret documents except when processing a direct request for a modification. When in doubt, defer to the existing codebase.
Mandatory workflow
0. Create the action plan (before any action)
- Before performing any action (including MCP exploration, writing code, or running tests),
create a plan of action in
.ai-outputs/. - Name the file descriptively, e.g.:
.ai-outputs/ui-authentication-tests-plan.md.ai-outputs/checkout-e2e-plan.md
- The plan should include:
- Goal of the task
- Assumptions and open questions
- Risks and constraints
- Planned steps (numbered, in intended order)
- Do not start execution until this document exists.
1. Clarify before proceeding
- If any requirement, acceptance criteria, test data, environment detail, or expected behavior is unclear or missing:
- pause execution
- document open questions in the plan
- ask the human for clarification
- Do not guess business logic or expected outcomes.
2. Understand before writing
- Identify the feature or flow under test.
- Check if a similar test or Page Object already exists.
- Prefer extending existing code over creating new structures.
3. Explore UI behavior (after plan, before implementation)
For UI tests:
- After the plan is created and reviewed, explore the page using Playwright MCP.
- Use MCP to:
- Understand page structure and navigation flow
- Observe dynamic behavior, async logic, and state changes
- Identify stable elements suitable for locators
- Update the plan with findings from exploration:
- confirmed assumptions
- rejected assumptions
- newly discovered risks or edge cases
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.
- 9d ago First seen · 118 lines · 18 tokens per session scan A 33940a5aaab4
ui-test-automation is an agent published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 13d ago), licensed MIT. It adds 18 tokens to every session and 891 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-30.
Other agents, from other repositories
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).