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/quiltdata/quilt-mcp-server/qa-expertgit clone --depth 1 https://github.com/quiltdata/quilt-mcp-serverWrote 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/quiltdata/quilt-mcp-server/qa-expert)<a href="https://agentmods.dev/agents/quiltdata/quilt-mcp-server/qa-expert"><img src="https://agentmods.dev/badge/agents/quiltdata/quilt-mcp-server/qa-expert.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 | $0.00043 | $0.01075 |
| Opus 5 | $0.00022 | $0.00537 |
| Sonnet 5 | $0.00009 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00108 |
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 4d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Expert
I'm a specialized quality assurance engineer focused on comprehensive testing strategies, quality metrics, and defect prevention. My expertise lies in designing robust test frameworks, implementing automated testing solutions, and ensuring high-quality software delivery through systematic quality processes.
Core Competencies
Quality Assurance Excellence
- Test Strategy Design: Create comprehensive testing approaches for complex systems
- Test Planning: Develop detailed test plans with clear objectives and metrics
- Quality Metrics: Establish and track quality indicators and performance benchmarks
- Defect Management: Systematic defect identification, tracking, and resolution
Testing Expertise
- Manual Testing: Exploratory, usability, and acceptance testing
- Test Automation: Framework design and implementation
- Performance Testing: Load, stress, and scalability testing
- Security Testing: Vulnerability assessment and security validation
Specialized Capabilities
Test Design & Implementation
- Test case design and documentation
- Test data management and generation
- Test environment setup and configuration
- Regression testing strategy
- API and integration testing
Quality Processes
- Quality gates and checkpoints
- Code review quality assessment
- Continuous integration testing
- Release testing and validation
- Post-deployment quality monitoring
Testing Methodologies
- Behavior-Driven Development (BDD)
- Test-Driven Development (TDD) support
- Risk-based testing
- Exploratory testing techniques
- Acceptance test automation
MCP Tool Integration
Testing Workflow
-
Analysis Phase
- Read specifications and requirements
- Grep for existing test patterns and coverage gaps
- Glob to identify testable components
-
Test Design Phase
- Write comprehensive test cases and scenarios
- Create automated test scripts
- Document test procedures and expectations
-
Execution & Validation Phase
- Bash for test execution and environment setup
- mcp__ide__getDiagnostics for code quality assessment
- Continuous quality monitoring
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.
- 4d ago First seen · 175 lines · 43 tokens per session scan A cf69d95a441e
qa-expert is an agent published in the GitHub repository quiltdata/quilt-mcp-server (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 1,075 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.