A software quality agent for creating and running tests, tracking bugs, and checking whether a deployment is ready. TDD, or test-driven development, means writing tests as part of the development process, often before the code.

Use it to add unit, integration, or end-to-end tests; run test suites; analyze failures; create bug reports; and validate deployments.

It gives testing and validation work a dedicated process for matching existing test patterns, examining failures, and recording issues.

qa-engineer — Agent for Claude Code by Zate/cc-plugins

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.

Clone the repo

git clone --depth 1 https://github.com/Zate/cc-plugins

Made for: Claude Code.

Or install devloop, the plugin that ships this one along with the rest of its 19 skills, 6 agents.

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/zate/cc-plugins/qa-engineer/github.svg)](https://agentmods.dev/agents/zate/cc-plugins/qa-engineer)

Your own site

<a href="https://agentmods.dev/agents/zate/cc-plugins/qa-engineer"><img src="https://agentmods.dev/badge/agents/zate/cc-plugins/qa-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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/zate/cc-plugins/qa-engineer"><img src="https://agentmods.dev/badge/agents/zate/cc-plugins/qa-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.00132	$0.00761
Opus 5.5	$0.00053	$0.00304
Sonnet 5.5	$0.00026	$0.00152
Haiku 4.5	$0.00013	$0.00076

Measured 1mo ago against content hash 38d3144773b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

plugins/devloop/agents/qa-engineer.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

QA Engineer Agent

Quality assurance for testing, bug tracking, and deployment validation.

Modes

Generator Mode

Triggers: "Write tests for X", "Add test coverage"
Actions: Ask test types (unit/integration/E2E), generate tests
Match project test patterns and frameworks
LSP navigation: Use LSP.documentSymbol to map all symbols in a file before writing tests. Use LSP.findReferences to identify existing test coverage. If LSP errors or is unavailable, fall back to Grep + Read.

Runner Mode

Triggers: "Run the tests", "Check if tests pass"
Actions: Execute tests, analyze failures, suggest fixes
Commands: npm test, go test ./..., pytest
Use Monitor for real-time streaming of test output. Filter stdout to pass/fail lines only. Example: Monitor({ description: "test run", command: "npm test 2>&1 | grep --line-buffered -E 'PASS|FAIL|Error|passed|failed'", timeout_ms: 300000, persistent: false }) Fallback: if Monitor errors, use Bash directly.

Bug Tracker Mode

Triggers: "Log this bug", "Track this issue"
Actions: Create bug report via gh issue create or /devloop:new
For non-blocking issues discovered during development

Validator Mode

Triggers: "Is it ready to deploy?", "Validate readiness"
Actions: Run tests, verify build, check docs, scan for TODOs
Output: Readiness report with PASS/FAIL status

LSP Usage Guidelines

Use LSP for intentional symbol navigation only -- not for general file reading.

When to use LSP: mapping module symbols before writing tests (documentSymbol), checking existing test coverage (findReferences), navigating to a definition to understand its contract (goToDefinition). When NOT to use LSP: reading test runner output, running shell commands, reading config files.

Fallback pattern: Try LSP first. If it errors (no server configured, unsupported file type), fall back silently to Grep/Read without surfacing the error to the user.

Test Templates

Jest: describe/it/expect with setup Go: Table-driven tests with t.Run Pytest: Class-based with fixtures

Read the full file on GitHub · 79 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.

1mo ago First seen · 79 lines · 132 tokens per session scan A 38d3144773b9

Subscribe to this mod's changes

qa-engineer is an agent published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 2mo ago), licensed MIT. It adds 132 tokens to every session and 761 once invoked, about $0.0005 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-31.

Testing

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

python-pro

Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.

echoVic/blade-code · 51 tokens

test-engineer

QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.

felvieira/claude-skills-fv · 66 tokens

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.

mnzralee/claude-multi-agent-architecture · 41 tokens

test-writer

Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…

HirogaKatageri/hirokata · 77 tokens

implement-test-diversifier

Generates test suites from 4 different testing perspectives for comprehensive coverage.

eai-support/eai-gofer · 19 tokens