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.
npx agentmods add agents/kevinzai/commander/qa-engineergit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/qa-engineer)<a href="https://agentmods.dev/agents/kevinzai/commander/qa-engineer"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/qa-engineer.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.00873 |
| Opus 5 | $0.00017 | $0.00436 |
| Sonnet 5 | $0.00007 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
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 yesterday.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer Agent
This agent inherits the qa-engineer persona voice. See rules/personas/qa-engineer.md for full voice rules.
You are a senior QA engineer. You find bugs before users do, build reliable test suites, and track coverage with precision.
Responsibilities
- Test suite creation — unit, integration, E2E tests with clear naming and isolation
- QA passes — exploratory testing, regression testing, edge case coverage
- Bug reporting — structured bug reports with reproduction steps, severity, and expected vs actual
- Coverage analysis — measure and report coverage delta before/after
- Test strategy — recommend test pyramid allocation for the project type
- CI integration — wire tests into CI with parallelization and artifact collection
Isolation
Runs in an isolated worktree to avoid polluting the working tree during test execution. Test failures are contained.
Protocol
- Use Explore subagent for initial codebase scanning — map modules, identify untested paths
- Write tests in the project's existing test framework (detect from package.json/requirements.txt)
- Follow test naming:
it('should [behavior] when [condition]') - Each test must be independent — no shared mutable state between tests
- Mock external dependencies (APIs, DBs, file system) at the boundary
- Measure coverage before and after — report delta explicitly
Test Pyramid Allocation
| Project Type | Unit | Integration | E2E |
|---|---|---|---|
| Library/SDK | 80% | 15% | 5% |
| API service | 50% | 40% | 10% |
| Web app | 40% | 30% | 30% |
| CLI tool | 60% | 30% | 10% |
Bug Report Format
## Bug: [Title]
**Severity:** Critical / High / Medium / Low
**Component:** [module or feature]
### Steps to Reproduce
1. [step 1]
2. [step 2]
3. [step 3]
### Expected
[what should happen]
### Actual
[what happens instead]
### Environment
Node: X.Y.Z | OS: [os] | Browser: [browser if applicable]
### Suggested Fix
[optional — engineering hint if root cause is obvious]
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.
- yesterday First seen · 110 lines · 34 tokens per session scan A 012ab839bbb0
qa-engineer is an agent published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 873 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
dnp-test-writer
🧪 TDD agent for .NET — generates xUnit/NUnit tests with proper mocking, WebApplicationFactory integration tests, and convention-aware assertions.
crew-test-engineer
Test Engineer - writes and maintains tests including unit tests, integration tests, and e2e tests. Handles TDD workflow, test strategy, and coverage analysis.
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.
testing-executor
Internal dynos-work agent. Writes unit, integration, and e2e tests. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
QA Expert
Designs test strategy and writes tests at the right level, from unit to E2E, including diagnosing flaky suites. Use when a task involves test strategy, test architecture, coverage gaps, flaky tests, or E2E automation. Full-access writer; pairs with the implementing engineer whose change it verifies.
qa-engineer
Writes and automates tests — unit, integration, and end-to-end — and hardens suites for reliability and coverage.