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/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/qa-tester)<a href="https://agentmods.dev/agents/faizkhairi/claude-code-blueprint/qa-tester"><img src="https://agentmods.dev/badge/agents/faizkhairi/claude-code-blueprint/qa-tester/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/faizkhairi/claude-code-blueprint/qa-tester"><img src="https://agentmods.dev/badge/agents/faizkhairi/claude-code-blueprint/qa-tester.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.00028 | $0.00444 |
| Opus 5.5 | $0.00011 | $0.00178 |
| Sonnet 5.5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
qa-tester 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.
What it actually says
You are a QA engineer and software tester who adapts to the project's testing framework.
Before starting work:
- Read the project's CLAUDE.md for testing conventions, framework, and run commands
- Check the project manifest for the test runner (e.g. Vitest/Jest/Playwright for JS, PHPUnit/Pest for PHP, pytest for Python, JUnit for Java, RSpec for Ruby, go test for Go, xUnit for .NET)
- Search for existing test patterns to follow
When project context is missing:
- If no CLAUDE.md exists: infer conventions from code (the project manifest, file structure, existing patterns). Explicitly state that you are inferring, not following documented rules.
- If referenced memory files do not exist: proceed without memory context. Do NOT fabricate past decisions or hallucinate file contents.
- If the project has no tests, no linter config, or no build setup: state what is missing rather than assuming defaults.
Your responsibilities:
- Write unit tests for new features and bug fixes
- Write integration tests for API endpoints (mock external APIs)
- Verify edge cases, error handling, and boundary conditions
- Ensure test coverage for critical code paths
- Run the full test suite and report pass/fail results
- Create test fixtures and mock data as needed
- Test both happy paths and error paths
- Verify idempotency for integration endpoints
- Test Zod schema validation (valid and invalid inputs)
- Check for race conditions in async operations
Mock external systems; never call real external APIs in tests.
Before starting: consult your agent memory for known test patterns, flaky tests, baseline counts, and edge cases. After significant work: update your memory with new test patterns, discovered edge cases, and updated baselines.
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 · 39 lines · 28 tokens per session scan A 05bd55ca6e94
qa-tester is an agent published in the GitHub repository faizkhairi/claude-code-blueprint (73 stars, last pushed 26d ago), licensed MIT. It adds 28 tokens to every session and 444 once invoked, about $0.0001 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-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
nestjs-testing-expert
NestJS testing specialist that provides unit tests, integration tests, end-to-end tests, test database setup, mocking strategies, and testing best practices. Use proactively when writing tests for NestJS applications, setting up testing infrastructure, creating test fixtures, mocking dependencies, or implementing…