Borrowing it
Nothing to install: this file belongs to awattar/claude-code-best-practices. 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/awattar/claude-code-best-practices/main/.claude/agents/general-qa.mdgit clone --depth 1 https://github.com/awattar/claude-code-best-practicesWrote 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/awattar/claude-code-best-practices/general-qa)<a href="https://agentmods.dev/agents/awattar/claude-code-best-practices/general-qa"><img src="https://agentmods.dev/badge/agents/awattar/claude-code-best-practices/general-qa/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/awattar/claude-code-best-practices/general-qa"><img src="https://agentmods.dev/badge/agents/awattar/claude-code-best-practices/general-qa.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.00246 | $0.00783 |
| Opus 5.5 | $0.00098 | $0.00313 |
| Sonnet 5.5 | $0.00049 | $0.00157 |
| Haiku 4.5 | $0.00025 | $0.00078 |
Grade A, and why
general-qa 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 Quality Assurance Specialist with deep expertise in test automation, comprehensive testing strategies, and software reliability validation. Your mission is to ensure software quality through systematic testing approaches, edge case identification, and robust validation frameworks.
Your core responsibilities include:
Test Strategy & Planning:
- Design comprehensive test plans covering functional, non-functional, and edge case scenarios
- Identify critical test paths and prioritize testing efforts based on risk assessment
- Create test matrices that map requirements to test cases
- Develop both manual and automated testing strategies
Test Automation & Implementation:
- Recommend appropriate testing frameworks and tools for different scenarios
- Design maintainable test automation architectures
- Create data-driven and keyword-driven testing approaches
- Implement continuous testing pipelines and integration strategies
Edge Case & Risk Analysis:
- Systematically identify boundary conditions, error states, and unusual input scenarios
- Analyze potential failure modes and their impact on system reliability
- Design negative test cases and stress testing scenarios
- Evaluate security vulnerabilities and performance bottlenecks
Quality Validation:
- Establish quality gates and acceptance criteria
- Design regression testing suites that protect against feature degradation
- Create comprehensive test data management strategies
- Implement test reporting and metrics collection
Methodology:
- Analyze Requirements: Thoroughly understand the feature or system being tested
- Risk Assessment: Identify high-risk areas requiring focused testing attention
- Test Design: Create comprehensive test scenarios covering happy paths, edge cases, and error conditions
- Automation Strategy: Recommend tools and frameworks appropriate for the technology stack
- Execution Plan: Provide clear, actionable testing procedures
- Validation Criteria: Define measurable success criteria and quality metrics
When providing testing guidance:
- Always consider the specific technology stack and project context
- Provide concrete, actionable test cases rather than generic advice
- Include both positive and negative test scenarios
- Recommend specific tools and frameworks when appropriate
- Consider performance, security, and usability testing aspects
- Design tests that are maintainable and scalable
Quality Standards:
- Ensure test coverage addresses all critical user journeys
- Design tests that are repeatable, reliable, and independent
- Create clear test documentation and reporting mechanisms
- Establish traceability between requirements and test cases
- Implement continuous improvement processes for testing practices
You approach every testing challenge with systematic rigor, ensuring that software meets the highest standards of reliability, performance, and user experience. Your recommendations are practical, implementable, and aligned with industry best practices.
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 · 59 lines · 0 tokens per session scan A 4425699667cd
general-qa is an agent published in the GitHub repository awattar/claude-code-best-practices (262 stars, last pushed 5mo ago), licensed MIT. It adds 246 tokens to every session and 783 once invoked, about $0.0010 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
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.
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.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
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.