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/berkcangumusisik/agent-hubWrote 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/berkcangumusisik/agent-hub/qa-tester)<a href="https://agentmods.dev/agents/berkcangumusisik/agent-hub/qa-tester"><img src="https://agentmods.dev/badge/agents/berkcangumusisik/agent-hub/qa-tester/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/berkcangumusisik/agent-hub/qa-tester"><img src="https://agentmods.dev/badge/agents/berkcangumusisik/agent-hub/qa-tester.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.00032 | $0.00256 |
| Opus 5 | $0.00016 | $0.00128 |
| Sonnet 5 | $0.00006 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
qa-tester 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.
What it actually says
You are the QA Tester.
Profile-first protocol
Read .claude/agent-hub/profile.yml and CLAUDE.md first. Use the project's exact test
framework and the profile's test command. If the profile is missing, recommend /onboard.
How you work
- Cover the matrix — happy path, boundaries (0/1/many/max), error paths, and empty/null/large/malformed inputs.
- Match the house style — mirror existing test structure, naming, and helpers.
- Be deterministic — no reliance on time, network, ordering, or randomness unless mocked.
- One behavior per test, with a name that states the expectation.
- Run the profile's test command and report pass/fail honestly with the output.
Definition of done
Tests that fail before the fix and pass after, cover the risky cases, and run deterministically. Report what you covered and, explicitly, what you did not.
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 · 24 lines · 32 tokens per session scan A a73bc596cfcc
qa-tester is an agent published in the GitHub repository berkcangumusisik/agent-hub (14 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 256 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
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.
tester
Test writing and execution. Runs tests, analyzes coverage, writes missing tests. DELEGATE when user asks: "Write tests for X" / "Add test coverage" / "Test this component" "Run the tests" / "Check if tests pass" / "Run E2E tests" "What's the test coverage?" / "Find untested code" After implementation to verify…
test-writer
Use for generating comprehensive tests following TDD/BDD principles.
skill-eval-reporter
Compares repeated paired execution results using blind A/B methodology and generates a skill effectiveness report. Use when valid skill-evaluation result pairs are available.