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/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/qa-engineer)<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/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/tranhieutt/software_development_department/qa-engineer"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/qa-engineer.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.00063 | $0.01067 |
| Opus 5.5 | $0.00025 | $0.00427 |
| Sonnet 5.5 | $0.00013 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00107 |
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.
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.
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 · 105 lines · 63 tokens per session scan A f2e8cdd03fb4
qa-engineer is an agent published in the GitHub repository tranhieutt/software_development_department (74 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 1,067 once invoked, about $0.0003 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-30.
Other agents, from other repositories
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
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.
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
engineer
Implementation specialist. Use for writing production code, refactoring, and TDD-driven feature work.
reviewer
Independent code reviewer. Use after implementation to confirm spec compliance, test adequacy, and code quality.
test
Tests developed features and reports pass/fail results with specific bug descriptions.