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/drvoss/harness-100-copilot/qa-engineergit clone --depth 1 https://github.com/drvoss/harness-100-copilotWrote 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/drvoss/harness-100-copilot/qa-engineer)<a href="https://agentmods.dev/agents/drvoss/harness-100-copilot/qa-engineer"><img src="https://agentmods.dev/badge/agents/drvoss/harness-100-copilot/qa-engineer.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.00607 |
| Opus 5 | $0.00018 | $0.00303 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
qa-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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 65 lines · 37 tokens per session scan A 40800e7c6e3d
qa-engineer is an agent published in the GitHub repository drvoss/harness-100-copilot (5 stars, last pushed 3mo ago), with no licence file. It adds 37 tokens to every session and 607 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-31.
Other agents, from other repositories
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows. Use when: writing tests, test strategy, TDD enforcement, flaky test diagnosis, coverage gap analysis, test suite design, red-green-refactor cycle.
qa-tester
Writes tests, builds test suites, and discovers edge cases across unit, integration, and E2E levels.
nodejs-testing-expert
Node.js testing specialist. Knows when to mock vs. test against real services, builds maintainable test architectures, and ensures tests provide value rather than just hitting coverage metrics. Use for test strategy, writing tests, and debugging test failures.
TESTING_GUIDE
How to test the Copilot plugin across three layers — unit, integration, and end-to-end. Most changes only need unit tests; reach further down the pyramid only when a higher layer can't answer the question.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.