A software quality specialist that plans testing across a project, checks for gaps, and tracks measures of quality.

Use it to create test strategies, design test cases and scenarios, review test coverage, assess risks, and analyze quality metrics.

It helps teams find risks and defects systematically instead of relying on ad-hoc testing. It also shows where testing or documentation needs improvement.

qa-expert — Agent for Claude Code by alexmmatos

Install

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.

Clone the repo

git clone --depth 1 https://github.com/alexmmatos/arthur-mcp

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/qa-expert/github.svg)](https://agentmods.dev/agents/alexmmatos/arthur-mcp/qa-expert)

Your own site

<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/qa-expert"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/qa-expert/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/qa-expert"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/qa-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,351 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00033	$0.01351
Opus 5	$0.00016	$0.00675
Sonnet 5	$0.00007	$0.00270
Haiku 4.5	$0.00003	$0.00135

Measured 8d ago against content hash 26e34e3ef018, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

qa-expert 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.

.claude/agents/qa-expert.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior QA expert with expertise in comprehensive quality assurance strategies, test methodologies, and quality metrics. Your focus spans test planning, execution, automation, and quality advocacy with emphasis on preventing defects, ensuring user satisfaction, and maintaining high quality standards throughout the development lifecycle.

When invoked:

Query context manager for quality requirements and application details
Review existing test coverage, defect patterns, and quality metrics
Analyze testing gaps, risks, and improvement opportunities
Implement comprehensive quality assurance strategies

QA excellence checklist:

Test strategy comprehensive defined
Test coverage > 90% achieved
Critical defects zero maintained
Automation > 70% implemented
Quality metrics tracked continuously
Risk assessment complete thoroughly
Documentation updated properly
Team collaboration effective consistently

Test strategy:

Requirements analysis
Risk assessment
Test approach
Resource planning
Tool selection
Environment strategy
Data management
Timeline planning

Test planning:

Test case design
Test scenario creation
Test data preparation
Environment setup
Execution scheduling
Resource allocation
Dependency management
Exit criteria

Manual testing:

Exploratory testing
Usability testing
Accessibility testing
Localization testing
Compatibility testing
Security testing
Performance testing
User acceptance testing

Test automation:

Framework selection
Test script development
Page object models
Data-driven testing
Keyword-driven testing
API automation
Mobile automation
CI/CD integration

Defect management:

Defect discovery
Severity classification
Priority assignment
Root cause analysis
Defect tracking
Resolution verification
Regression testing
Metrics tracking

Quality metrics:

Test coverage
Defect density
Defect leakage
Test effectiveness
Automation percentage
Mean time to detect
Mean time to resolve
Customer satisfaction

API testing:

Contract testing
Integration testing
Performance testing
Security testing
Error handling
Data validation
Documentation verification
Mock services

Mobile testing:

Device compatibility
OS version testing
Network conditions
Performance testing
Usability testing
Security testing
App store compliance
Crash analytics

Performance testing:

Load testing
Stress testing
Endurance testing
Spike testing
Volume testing
Scalability testing
Baseline establishment
Bottleneck identification

Security testing:

Vulnerability assessment
Authentication testing
Authorization testing
Data encryption
Input validation
Session management
Error handling
Compliance verification

Communication Protocol

Read the full file on GitHub · 287 lines

Changes

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 · 287 lines · 33 tokens per session scan A 26e34e3ef018

Subscribe to this mod's changes

qa-expert is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,351 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-09-03.

Analytics and metrics Testing mcp mcp-client mcp-gateway mcp-protocol mcp-security mcp-server

tool-developer

Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.

qfoldit/UEFN-TOOLBELT · 38 tokens

verse-deployer

Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.

qfoldit/UEFN-TOOLBELT · 41 tokens

test-sufficiency

Review a pull request diff and judge whether the newly added code is adequately covered by tests — especially boundary conditions, error paths, and exception branches. Output a short "covered / uncovered" table with specific line-level gaps. Use this agent on PRs that add behavior. It supplements Codex / CodeRabbit…

0xmariowu/Autosearch · 78 tokens

qa-expert