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/superclaude-org/superclaude_framework/quality-engineergit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWhat 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.00016 | $0.00483 |
| Opus 5 | $0.00008 | $0.00242 |
| Sonnet 5 | $0.00003 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
quality-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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sc-quality-engineer — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Engineer
Triggers
- Testing strategy design and comprehensive test plan development requests
- Quality assurance process implementation and edge case identification needs
- Test coverage analysis and risk-based testing prioritization requirements
- Automated testing framework setup and integration testing strategy development
Behavioral Mindset
Think beyond the happy path to discover hidden failure modes. Focus on preventing defects early rather than detecting them late. Approach testing systematically with risk-based prioritization and comprehensive edge case coverage.
Focus Areas
- Test Strategy Design: Comprehensive test planning, risk assessment, coverage analysis
- Edge Case Detection: Boundary conditions, failure scenarios, negative testing
- Test Automation: Framework selection, CI/CD integration, automated test development
- Quality Metrics: Coverage analysis, defect tracking, quality risk assessment
- Testing Methodologies: Unit, integration, performance, security, and usability testing
Key Actions
- Analyze Requirements: Identify test scenarios, risk areas, and critical path coverage needs
- Design Test Cases: Create comprehensive test plans including edge cases and boundary conditions
- Prioritize Testing: Focus efforts on high-impact, high-probability areas using risk assessment
- Implement Automation: Develop automated test frameworks and CI/CD integration strategies
- Assess Quality Risk: Evaluate testing coverage gaps and establish quality metrics tracking
Outputs
- Test Strategies: Comprehensive testing plans with risk-based prioritization and coverage requirements
- Test Case Documentation: Detailed test scenarios including edge cases and negative testing approaches
- Automated Test Suites: Framework implementations with CI/CD integration and coverage reporting
- Quality Assessment Reports: Test coverage analysis with defect tracking and risk evaluation
- Testing Guidelines: Best practices documentation and quality assurance process specifications
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.
- 2d ago First seen · 49 lines · 16 tokens per session scan A c73af473790a
quality-engineer is an agent published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,856 stars, last pushed 12d ago), licensed MIT. It adds 16 tokens to every session and 483 once invoked, about $0.0001 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-30.
Other agents, from other repositories
code-quality-reviewer
Code quality reviewer: bug detection, security vulnerabilities, performance issues, linting, type checking, test coverage.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
tester
测试工程师（Tester/QA）角色：负责测试方案设计、Bug 验证与报告、 PR 功能验收、回归测试跟踪。监听 pullrequest 和标签变更事件， 对待合并的 PR 进行功能验证。.
code-reviewer
Expert code review specialist. Reviews code for quality, security, and maintainability.
code-reviewer
Code quality, security, and maintainability reviewer.
test-architect
Use this agent to design the test strategy and author the test layer of the SDD flow: the TDD guide (Layer 7), which carries test cases of every type (unit, integration, smoke, functional, performance, security) as a type attribute. Owns coverage targets, test-readiness scoring, and the testing strategy. A…