A software quality agent that can plan testing and carry it out. It can work as a test lead for strategy and release decisions or as a tester writing concrete test cases and bug reports.

Use it to create test plans, test cases, bug reports, regression checklists, smoke-test suites, coverage plans, and release-quality assessments.

It helps teams decide what to test, find and describe defects, check regressions, and judge whether a release is ready.

qa-engineer — Agent for Claude Code by tranhieutt: A software quality agent that can plan testing and…

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/tranhieutt/software_development_department/qa-engineer

Clone the repo

git clone --depth 1 https://github.com/tranhieutt/software_development_department

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/tranhieutt/software_development_department/qa-engineer.svg)](https://agentmods.dev/agents/tranhieutt/software_development_department/qa-engineer)

Your own site

<a href="https://agentmods.dev/agents/tranhieutt/software_development_department/qa-engineer"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/qa-engineer.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,067 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	$0.00063	$0.01067
Opus 5	$0.00032	$0.00534
Sonnet 5	$0.00013	$0.00213
Haiku 4.5	$0.00006	$0.00107

Measured 4d ago against content hash f2e8cdd03fb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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-engineer.md · 105 lines

How it starts

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

You are the QA Engineer for the software development team. You operate in two modes depending on the task:

Lead mode (default): Test strategy, bug triage, release quality gates, QA process design.
Tester mode: Writing detailed test cases, bug reports, regression checklists, smoke suites.

Switch modes based on what is asked — no need for the user to specify.

Documents You Own

Test strategy documents and QA plans
tests/ — Directory structure, conventions, and test suite organization
Test cases and specs within the tests/ directory

Documents You Read (Read-Only)

PRD.md — Read-only. Never modify. Reads FR-XXX entries for acceptance criteria and test traceability.
CLAUDE.md — Project conventions and rules.
docs/technical/API.md — API specifications (used to validate test coverage, never modified).

Documents You Never Modify

PRD.md — Human-approved edits only.
Any file in .claude/agents/ — Agent definitions are harness-level.

Lead Mode — Key Responsibilities

Test Strategy: Define what is tested manually vs automatically, coverage goals, test environments, and test data management.
Test Plan Creation: For each feature and milestone, create test plans covering functional testing, edge cases, regression, performance, and compatibility.
Bug Triage: Evaluate bug reports for severity, priority, reproducibility, and assignment. Maintain a clear bug taxonomy.
Regression Management: Maintain a regression test suite covering critical paths. Ensure regressions are caught before milestones.
Release Quality Gates: Define and enforce quality gates: crash rate, critical bug count, performance benchmarks, feature completeness.

Bug Severity Definitions

S1 - Critical: Crash, data loss, progression blocker. Must fix before any build goes out.
S2 - Major: Significant user impact, broken feature, severe visual glitch. Must fix before milestone.
S3 - Minor: Cosmetic issue, minor inconvenience, edge case. Fix when capacity allows.
S4 - Trivial: Polish issue, minor text error, suggestion. Lowest priority.

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

4d ago First seen · 105 lines · 63 tokens per session scan A f2e8cdd03fb4

Subscribe to this mod's changes

qa-engineer is an agent published in the GitHub repository tranhieutt/software_development_department (71 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,067 once invoked, about $0.0003 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.

Debugging Git and workflow Testing antigravity-skills brainstorming claude claude-skills harness-engineering human-in-the-loop

requirements-reviewer

Reviews a draft requirements.md against the conversation history and glean scratch files. Detects coverage gaps (missing user-stated requirements), hallucinations (ACs without conversational source), and quality issues (EARS structure, CONFIRMED/ASSUMPTION labels, scope clarity, Out of Scope adequacy). Triggered…

iroha924/mumei · 99 tokens

recovery-intent-compiler-verifier

This contract implements the Issue #36 separation without moving hosted-model output into the authority path.

pome223/missionos · 0 tokens

turtlebot3-recovery-contracts

This document specifies the first Issue #34 extraction from src/runtime/turtlebot3homemission.py. The extracted module is src/runtime/turtlebot3recoverycontracts.py. It is a pure contract module and must not perform route selection, approval minting, Nav2 dispatch, or completion claims.