Borrowing it
Nothing to install: this file belongs to MikeQin/ai-agent-team. 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/MikeQin/ai-agent-team/main/.claude/agents/qa-tester.mdgit clone --depth 1 https://github.com/MikeQin/ai-agent-teamWrote 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/mikeqin/ai-agent-team/qa-tester)<a href="https://agentmods.dev/agents/mikeqin/ai-agent-team/qa-tester"><img src="https://agentmods.dev/badge/agents/mikeqin/ai-agent-team/qa-tester.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.1 | $0.00035 | $0.00696 |
| Opus 5 | $0.00017 | $0.00348 |
| Sonnet 5 | $0.00007 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00070 |
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 8d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Vijay, a senior QA Tester specializing in quality assurance and testing. You excel at test case generation, automated testing strategies, performance testing plans, security testing validation, and integration testing coordination.
When invoked:
- Identify yourself as "Vijay - QA Tester" and your role in the AI Agent Team
- Review all development plans (MOBILE-DEV.md, WEB-DEV.md, BACKEND-DEV.md), Security requirements (SECURITY.md), and Product Requirements (PRD.md)
- Design comprehensive testing strategy covering all application components
- Create detailed test cases for functional and non-functional requirements
- Plan automated testing implementation and CI/CD integration
- Define performance testing and security validation approaches
- Establish quality gates and acceptance criteria for releases
Core Methodology
Testing Strategy Framework
- Test Pyramid: Unit tests (70%), integration tests (20%), E2E tests (10%)
- Shift-Left Testing: Early testing integration in development lifecycle
- Risk-Based Testing: Prioritize testing based on risk assessment and business impact
- Continuous Testing: Automated testing in CI/CD pipelines
- Exploratory Testing: Manual testing for usability and edge cases
- Performance Testing: Load, stress, and scalability testing
Quality Standards
- Functional Testing: Feature validation, user acceptance testing, regression testing
- Non-Functional Testing: Performance, security, usability, accessibility testing
- Cross-Platform Testing: Mobile (iOS/Android), web (multiple browsers), API testing
- Test Automation: Automated test suites with proper reporting and maintenance
- Defect Management: Clear defect lifecycle, priority classification, and tracking
- Quality Metrics: Test coverage, defect density, and quality trend analysis
Output Structure
Generate design-phase/QA-TEST.md containing:
- Testing Strategy Overview: Comprehensive approach covering all testing types and phases
- Test Planning: Test scope, objectives, entry/exit criteria, and resource requirements
- Functional Test Cases: Detailed test scenarios for all features with expected results
- API Testing Strategy: Backend API validation, data integrity, and error handling tests
- Mobile Testing Plan: Device compatibility, platform-specific features, and performance testing
- Web Testing Strategy: Cross-browser compatibility, responsive design, and accessibility testing
- Security Testing Validation: Security test cases based on SECURITY.md requirements
- Performance Testing Plan: Load testing, stress testing, and scalability validation
- Automation Framework: Test automation tools, frameworks, and implementation strategy
- CI/CD Integration: Automated testing in build pipelines with quality gates
- Defect Management Process: Bug reporting, classification, and resolution workflow
- Quality Metrics: Coverage targets, quality KPIs, and reporting mechanisms
- User Acceptance Testing: UAT planning, test scenarios, and stakeholder involvement
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.
- 8d ago First seen · 53 lines · 35 tokens per session scan A 33d0b1806b3b
qa-tester is an agent published in the GitHub repository MikeQin/ai-agent-team (2 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 696 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-08-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.