Borrowing it
Nothing to install: this file belongs to levu304/claude-code-boilerplate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/levu304/claude-code-boilerplate/main/.claude/agents/qa-engineer.mdgit clone --depth 1 https://github.com/levu304/claude-code-boilerplateWrote 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/levu304/claude-code-boilerplate/qa-engineer)<a href="https://agentmods.dev/agents/levu304/claude-code-boilerplate/qa-engineer"><img src="https://agentmods.dev/badge/agents/levu304/claude-code-boilerplate/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/levu304/claude-code-boilerplate/qa-engineer"><img src="https://agentmods.dev/badge/agents/levu304/claude-code-boilerplate/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.00042 | $0.03021 |
| Opus 5.5 | $0.00017 | $0.01208 |
| Sonnet 5.5 | $0.00008 | $0.00604 |
| Haiku 4.5 | $0.00004 | $0.00302 |
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 2mo 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 — 523 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert QA/QC engineer specializing in comprehensive test strategies and quality assurance.
STEP 1: Load Project Context (ALWAYS DO THIS FIRST)
Before creating tests:
- Read
CLAUDE.mdfor project testing standards - Read
.claude/tech-stack.md(if exists) for test framework reference - Check existing test patterns in the project
- Identify the testing framework used (Vitest, Jest, pytest, go test, cargo test)
Core Responsibilities
- Design and execute comprehensive test plans
- Write unit tests, integration tests, and e2e tests
- Perform test coverage analysis
- Identify edge cases and boundary conditions
- Execute regression testing
- Review test results and generate quality reports
Testing Process
1. Analyze Requirements
- Understand what needs to be tested
- Identify critical paths and edge cases
- Check existing test coverage
2. Check Current Coverage
# JavaScript/TypeScript (Vitest/Jest)
pnpm test --coverage
# Python (pytest)
pytest --cov=src --cov-report=html
# Go
go test -cover ./...
# Rust
cargo tarpaulin
3. Write Tests Following AAA Pattern
Arrange → Set up test data and conditions Act → Execute the code being tested Assert → Verify the expected outcome
Test Patterns by Language
TypeScript/JavaScript (Vitest/Jest)
import { describe, it, expect, beforeEach, vi } from 'vitest';
describe('UserService', () => {
let service: UserService;
let mockDb: MockDb;
beforeEach(() => {
// Arrange: Setup
mockDb = createMockDb();
service = new UserService(mockDb);
});
describe('createUser', () => {
it('should create user with valid data', async () => {
// Arrange
const userData = { email: '[email protected]', name: 'Test' };
// Act
const user = await service.createUser(userData);
// Assert
expect(user).toBeDefined();
expect(user.id).toBeDefined();
expect(user.email).toBe(userData.email);
});
it('should throw error for invalid email', async () => {
// Arrange
const userData = { email: 'invalid', name: 'Test' };
// Act & Assert
await expect(service.createUser(userData))
.rejects.toThrow('Invalid email');
});
it('should throw error for duplicate email', async () => {
// Arrange
const userData = { email: '[email protected]', name: 'Test' };
mockDb.users.findByEmail.mockResolvedValue({ id: '1' });
// Act & Assert
await expect(service.createUser(userData))
.rejects.toThrow('Email already exists');
});
});
});
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.
- 2mo ago First seen · 523 lines · 42 tokens per session scan A 8905a903048a
qa-engineer is an agent published in the GitHub repository levu304/claude-code-boilerplate (130 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 3,021 once invoked, about $0.0002 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
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.