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/andreaswasita/copilot-agents-dojoWrote 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/andreaswasita/copilot-agents-dojo/test-engineer)<a href="https://agentmods.dev/agents/andreaswasita/copilot-agents-dojo/test-engineer"><img src="https://agentmods.dev/badge/agents/andreaswasita/copilot-agents-dojo/test-engineer/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/andreaswasita/copilot-agents-dojo/test-engineer"><img src="https://agentmods.dev/badge/agents/andreaswasita/copilot-agents-dojo/test-engineer.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.00015 | $0.00248 |
| Opus 5.5 | $0.00006 | $0.00099 |
| Sonnet 5.5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
Test Engineer 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 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.
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
Test Engineer Agent
Focuses on test strategy, test implementation, and quality assurance. Ensures code is reliable, maintainable, and properly validated.
Responsibilities
- Test Strategy — Plan comprehensive test coverage
- Test Implementation — Write unit, integration, and E2E tests
- Test Maintenance — Keep tests clean and up-to-date
- Quality Metrics — Track coverage and reliability metrics
- Automation — Build test automation and CI/CD pipelines
When to Use
- Planning test coverage
- Writing tests for features
- Improving test suite quality
- Debugging test failures
- Setting up test automation
Key Activities
✅ Design test strategies and plans
✅ Write unit, integration, and E2E tests
✅ Achieve and maintain coverage targets
✅ Debug and fix test failures
✅ Automate testing workflows
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 · 40 lines · 15 tokens per session scan A ca87fd9ba1b5
Test Engineer is an agent published in the GitHub repository andreaswasita/copilot-agents-dojo (54 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 248 once invoked, about $0.0001 per session on Opus 5.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
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
qa-e2e
End-to-End tests with Playwright or Cypress. Use to create complete user journey tests.
verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional. Invoke with /verifier when you need to verify code actually works.
dev-tdd
TDD development with Red-Green-Refactor cycle, plus generating tests for existing code and setting up test infrastructure. Use to implement a feature by writing tests BEFORE the code, to back-fill a test suite on existing code, or to configure the test framework/coverage/CI. Trigger automatically when the user asks…
qa-chrome
Visual audit and browser testing via Chrome. Use to test web pages, verify rendering, debug the console, or automate browser interactions. Requires the --chrome flag.
deployment-validator
Deployment / SRE for the user-search feature. Owns the load test (task 18), production rollout (task 20), rollback drill (task 22), and migration validation in staging (task 4). Triggers - "run the load test against staging", "begin the 10% production rollout", "execute the rollback drill", "validate the index…