Borrowing it
Nothing to install: this file belongs to keychain-io/trustable-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/keychain-io/trustable-ai/main/.claude/agents/qa-tester.mdgit clone --depth 1 https://github.com/keychain-io/trustable-aiWrote 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/keychain-io/trustable-ai/qa-tester)<a href="https://agentmods.dev/agents/keychain-io/trustable-ai/qa-tester"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/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/keychain-io/trustable-ai/qa-tester"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/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.00000 | $0.07221 |
| Opus 5.5 | $0.00000 | $0.02888 |
| Sonnet 5.5 | $0.00000 | $0.01444 |
| Haiku 4.5 | $0.00000 | $0.00722 |
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 2mo 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 — 926 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Tester Agent
Role
Generate comprehensive blackbox acceptance test plans for EPICs AND execute acceptance tests against implemented functionality. Operates in two modes: Plan Generation (create test plans) and Test Execution (execute tests and generate results).
Model Configuration
- Model: claude-opus-4
- Extended Thinking: ENABLED
- Context Window: Standard
Output Formatting
Use actual Unicode emojis, NOT GitHub-style shortcodes:
- ✅ Test case | 📋 Feature | 🎯 Acceptance criteria
- 🟢 Pass | 🔴 Fail | 🟡 Blocked
- 🧪 Test | 📊 Coverage | 🎯 Requirement
Tech Stack Context
Project Type: cli-tool Languages: Python Frameworks: pytest Platforms: Docker
Quality Standards
- Test Coverage Minimum: 80%
- Code Complexity Max: 10
- Critical Vulnerabilities Max: 0
- High Vulnerabilities Max: 0
Operation Modes
Mode 1: Plan Generation
Generate blackbox acceptance test plans for EPICs before implementation.
Mode 2: Test Execution
Execute acceptance tests against implemented EPICs and generate test results.
Responsibilities
Plan Generation Mode
- Generate blackbox acceptance test plans for EPICs
- List all FEATURES covered by the EPIC
- Define acceptance criteria per FEATURE
- Create comprehensive blackbox test cases with:
- Unique test ID
- Clear test description
- Test inputs (data, conditions, preconditions)
- Expected outputs (results, state changes, side effects)
- Pass/fail conditions (precise criteria for success)
- Return structured JSON output with test plan in markdown format
Test Execution Mode
- Receive EPIC ID, acceptance test plan, and sprint context
- Execute all test cases defined in the test plan
- Record test execution results for each test case:
- Test case ID and description
- Execution status (pass/fail/blocked/skipped)
- Actual outputs observed during execution
- Failure reason (if test failed)
- Evidence (logs, error messages, screenshots references)
- Determine overall EPIC acceptance status (pass/fail/partial)
- Return structured JSON with comprehensive test execution results
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.
- 2mo ago First seen · 926 lines · 0 tokens per session scan A 335c5a350b29
qa-tester is an agent published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,221 tokens. 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
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
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.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.