An agent role that creates black-box acceptance test plans for large work items and runs those tests against implemented features. Black-box testing checks behavior without relying on the code's internal structure.

Use it to plan tests before implementation, execute them afterward, list covered features and acceptance criteria, and report results for Python projects using pytest.

It helps compare completed functionality with requirements and records whether each acceptance test passes, fails, or is blocked.

qa-tester — Agent for Claude Code by keychain-io: An agent role that creates black-box acceptance test plans…

Install

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.

agentmods

npx agentmods add agents/keychain-io/trustable-ai/qa-tester

Clone the repo

git clone --depth 1 https://github.com/keychain-io/trustable-ai

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/keychain-io/trustable-ai/qa-tester.svg)](https://agentmods.dev/agents/keychain-io/trustable-ai/qa-tester)

Your own site

<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="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 7,221 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.03610
Sonnet 5	$0.00000	$0.01444
Haiku 4.5	$0.00000	$0.00722

Measured 5d ago against content hash 335c5a350b29, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

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 5d 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.

.claude/agents/qa-tester.md · 926 lines

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

Read the full file on GitHub · 926 lines

Changes

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.

5d ago First seen · 926 lines · 0 tokens per session scan A 335c5a350b29

Subscribe to this mod's changes

qa-tester is an agent published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 6mo 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.

E2E testing Testing

qa

Use when testing application quality via browser dogfood, E2E tests, or API smoke tests. Navigates the app with the available browser tool, takes screenshots, checks console errors, and runs relevant E2E tests. Read-only — reports issues but never edits code. Also use when the user says 'test this', 'dogfood', 'QA'…

exceptionless/Exceptionless · 85 tokens

e2e-verifier

FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.

K9i-0/ccpocket · 65 tokens

test-reporter

Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.

nrslib/takt · 0 tokens

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…

eunomia-bpf/agentsight · 0 tokens

ask-smoke

Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…

Endle/fireSeqSearch · 100 tokens

electron-e2e-test-runner

Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…

sahithvibudhi/vibe-tree · 365 tokens