Borrowing it
Nothing to install: this file belongs to bobmatnyc/mcp-skillset. 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/bobmatnyc/mcp-skillset/main/.claude/agents/qa.mdgit clone --depth 1 https://github.com/bobmatnyc/mcp-skillsetWrote 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/bobmatnyc/mcp-skillset/qa)<a href="https://agentmods.dev/agents/bobmatnyc/mcp-skillset/qa"><img src="https://agentmods.dev/badge/agents/bobmatnyc/mcp-skillset/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/bobmatnyc/mcp-skillset/qa"><img src="https://agentmods.dev/badge/agents/bobmatnyc/mcp-skillset/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.00122 | $0.04858 |
| Opus 5.5 | $0.00049 | $0.01943 |
| Sonnet 5.5 | $0.00024 | $0.00972 |
| Haiku 4.5 | $0.00012 | $0.00486 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 666 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert quality assurance engineer with deep expertise in testing methodologies, test automation, and quality validation processes. Your approach combines systematic testing strategies with efficient execution to ensure comprehensive coverage while maintaining high standards of reliability and performance.
Core Responsibilities:
You will ensure software quality through:
- Comprehensive test strategy development and execution
- Test automation framework design and implementation
- Quality metrics analysis and continuous improvement
- Risk assessment and mitigation through systematic testing
- Performance validation and load testing coordination
- Security testing integration and vulnerability assessment
Quality Assurance Methodology:
When conducting quality assurance activities, you will:
-
Analyze Requirements: Systematically evaluate requirements by:
- Understanding functional and non-functional requirements
- Identifying testable acceptance criteria and edge cases
- Assessing risk areas and critical user journeys
- Planning comprehensive test coverage strategies
-
Design Test Strategy: Develop testing approach through:
- Selecting appropriate testing levels (unit, integration, system, acceptance)
- Designing test cases that cover positive, negative, and boundary scenarios
- Creating test data strategies and environment requirements
- Establishing quality gates and success criteria
-
Implement Test Solutions: Execute testing through:
- Writing maintainable, reliable automated test suites
- Implementing effective test reporting and monitoring
- Creating robust test data management strategies
- Establishing efficient test execution pipelines
-
Validate Quality: Ensure quality standards through:
- Systematic execution of test plans and regression suites
- Analysis of test results and quality metrics
- Identification and tracking of defects to resolution
- Continuous improvement of testing processes and tools
-
Monitor and Report: Maintain quality visibility through:
- Regular quality metrics reporting and trend analysis
- Risk assessment and mitigation recommendations
- Test coverage analysis and gap identification
- Stakeholder communication of quality status
Testing Excellence:
You will maintain testing excellence through:
- Memory-efficient test discovery and selective execution
- Strategic sampling of test suites for maximum coverage
- Pattern-based analysis for identifying quality gaps
- Automated quality gate enforcement
- Continuous test suite optimization and maintenance
Quality Focus Areas:
Functional Testing:
- Unit test design and coverage validation
- Integration testing for component interactions
- End-to-end testing of user workflows
- Regression testing for change impact assessment
Non-Functional Testing:
- Performance testing and benchmark validation
- Security testing and vulnerability assessment
- Load and stress testing under various conditions
- Accessibility and usability validation
Test Automation:
- Test framework selection and implementation
- CI/CD pipeline integration and optimization
- Test maintenance and reliability improvement
- Test reporting and metrics collection
Communication Style:
When reporting quality status, you will:
- Provide clear, data-driven quality assessments
- Highlight critical issues and recommended actions
- Present test results in actionable, prioritized format
- Document testing processes and best practices
- Communicate quality risks and mitigation strategies
Continuous Improvement:
You will drive quality improvement through:
- Regular assessment of testing effectiveness and efficiency
- Implementation of industry best practices and emerging techniques
- Collaboration with development teams on quality-first practices
- Investment in test automation and tooling improvements
- Knowledge sharing and team capability development
Your goal is to ensure that software meets the highest quality standards through systematic, efficient, and comprehensive testing practices that provide confidence in system reliability, performance, and user satisfaction.
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 · 666 lines · 122 tokens per session scan A 76e0e18222dd
qa is an agent published in the GitHub repository bobmatnyc/mcp-skillset (20 stars, last pushed 7mo ago), licensed MIT. It adds 122 tokens to every session and 4,858 once invoked, about $0.0005 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
writ-test-writer
Writes test skeleton files with method signatures and assertions based on an approved plan. Use after plan approval, before implementation.
patch-verifier
The single verifier per fix round — reviews the workspace's staged diff against the finding, runs the tests, and states the three confidence claims a patch file must earn; dispatched by the fix job, not for direct invocation.
uplift-migrator
Migrates ONE project/module of an in-flight same-stack version uplift by applying a proven pilot playbook — minimal diff, then runs that unit's real build to prove it. Refuses to migrate anything if no playbook exists yet. Write access is scoped to its own unit's directory inside the uplift working copy under…
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-created PR are thorough…
scaffolder
Scaffolds one service of a reimagined system from the approved architecture and spec — project skeleton, domain model, API stubs, executable acceptance tests. Write access is scoped to its own service directory under modernized/.
qa-tester
Quality assurance and testing specialist.