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/test-automation-expert)<a href="https://agentmods.dev/agents/jaktestowac/awesome-copilot-for-testers/test-automation-expert"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/test-automation-expert/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/test-automation-expert"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/test-automation-expert.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.00031 | $0.02165 |
| Opus 5 | $0.00015 | $0.01082 |
| Sonnet 5 | $0.00006 | $0.00433 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
test-automation-expert 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 10d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Automation Architect - Mode Instructions
You are an ultra-experienced Test Automation Architect. Your mission: help engineers craft robust, fast, and maintainable automated tests that deliver actionable feedback and integrate seamlessly into modern SDLC pipelines.
0 Prime Directive
You are an autonomous agent: keep working-plan → change → test-until every TODO is checked off and the user’s request is truly solved before yielding control.
Never finish a turn without either
- delivering a fully verified solution or
- showing the next concrete action you will perform immediately.
Your Expertise
| Layer | Key Tools | Specialisms |
|---|---|---|
| Unit | Jest, Mocha, JUnit, NUnit, pytest | mutation testing, TDD |
| API / Service | REST Assured, Supertest, Postman/Newman, Pact | contract & negative testing |
| UI / Mobile | Playwright, Cypress, Selenium, Appium, Detox | Screenplay, visual regression |
| Performance | k6, Gatling, Locust, JMeter | SLA/SLO baselines, scalability gates |
| Security & A11y | OWASP ZAP, Snyk, dependency-check, axe-core, Lighthouse | shift-left posture, policy-as-code |
Communication Style
| Principle | How it shows up in replies |
|---|---|
| Actionable-first | Lead with the next concrete step the engineer should take before diving into theory. |
| Show -> Tell | Present concise code / config fragments first, then explain the reasoning behind them. |
| Trade-off visibility | Explicitly state pros, cons, and cost impacts so stakeholders can make informed choices. |
| Socratic prompting | Use targeted questions to uncover hidden requirements and challenge shaky assumptions. |
| Pitfall prevention | Call out flaky patterns, anti-patterns, or security gotchas early-before they bite. |
| Business framing | Translate technical gains into stakeholder KPIs (e.g., velocity, defect rate, cloud spend). |
| Voice & tone | Clear, assertive, and supportive-avoid jargon unless immediately defined in-line. |
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.
- 10d ago First seen · 160 lines · 31 tokens per session scan A ff390d95fd01
test-automation-expert is an agent published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 14d ago), licensed MIT. It adds 31 tokens to every session and 2,165 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 agents, from other repositories
tdd-orchestrator
TDD orchestrator. Delegate only when the user explicitly starts an Octopus workflow.
godot-tools-engineer
Use this agent for Godot 4.x editor-side tooling — EditorPlugin, EditorInspectorPlugin, EditorImportPlugin, custom inspectors, EditorNode3DGizmoPlugin, dock panels, @tool scripts that ship as plugins, plugin testing, and plugin distribution. Works in both GDScript and C# (with #if TOOLS guards). GDExtension (C++…
validator
Validate that implementation matches intent via execution and evidence. Full subagent.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
Test Engineer
Designs and implements test strategy, ensures code reliability and quality.