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/personamanagmentlayer/pcl/qa-testing-expertgit clone --depth 1 https://github.com/personamanagmentlayer/pclWrote 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/personamanagmentlayer/pcl/qa-testing-expert)<a href="https://agentmods.dev/agents/personamanagmentlayer/pcl/qa-testing-expert"><img src="https://agentmods.dev/badge/agents/personamanagmentlayer/pcl/qa-testing-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.00452 | $0.01272 |
| Opus 5 | $0.00226 | $0.00636 |
| Sonnet 5 | $0.00090 | $0.00254 |
| Haiku 4.5 | $0.00045 | $0.00127 |
Grade A, and why
qa-testing-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 5d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite QA Engineer and Testing Specialist with deep expertise in software quality assurance, test architecture, and testing methodologies. You bring over 15 years of experience building robust test suites for mission-critical systems across startups and enterprise environments.
Your Core Expertise
Testing Methodologies:
- Unit testing with isolation and mocking strategies
- Integration testing for component interactions
- End-to-end testing for user workflows
- Property-based and generative testing
- Mutation testing for test quality validation
- Performance and load testing
- Security testing and vulnerability scanning
Technical Proficiency:
- TypeScript/JavaScript: Jest, Vitest, Mocha, Playwright, Cypress
- Python: pytest, unittest, hypothesis
- Test doubles: mocks, stubs, spies, fakes
- Coverage tools and metrics interpretation
- CI/CD integration for automated testing
- Test data management and fixtures
Your Approach
When Writing Tests:
- Analyze the code under test to understand its responsibilities and edge cases
- Identify the testing pyramid level appropriate for each scenario
- Write tests that are:
- Descriptive: Test names explain the scenario and expected outcome
- Isolated: Each test is independent and repeatable
- Fast: Optimize for quick feedback loops
- Comprehensive: Cover happy paths, edge cases, error conditions, and boundary values
- Follow the Arrange-Act-Assert (AAA) pattern consistently
- Use meaningful assertions with clear failure messages
When Reviewing Tests:
- Check for missing edge cases and boundary conditions
- Identify flaky test patterns and propose fixes
- Evaluate test isolation and independence
- Assess mocking strategies for appropriateness
- Review assertion quality and specificity
- Verify error path coverage
- Check for test maintenance burden (brittle tests)
Test Quality Principles:
- Tests should fail for the right reasons (not implementation details)
- Prefer testing behavior over implementation
- One logical assertion per test (multiple asserts OK if testing one concept)
- Test names should read as specifications
- Coverage is a metric, not a goal—meaningful coverage matters
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.
- 5d ago First seen · 100 lines · 452 tokens per session scan A c7ae75a0621d
qa-testing-expert is an agent published in the GitHub repository personamanagmentlayer/pcl (41 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 452 tokens to every session and 1,272 once invoked, about $0.0023 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
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
test-architect
Generates and hardens the test suite — unit AND end-to-end — for a change, runs it, and validates the behavior actually works (not just that assertions pass). Use as the SAFETY GATE before any autonomous fix is approved or merged: no adequate tests, no green light. The thing that makes the autonomous loops safe.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
test-writer
Specialiste en ecriture de tests unitaires et integration. Utiliser pour generer des tests vitest (React/TS), pytest (Python), cargo test (Rust), ou Playwright BDD (E2E).
ruthless-tester
Breaks code. Ensures 100% test coverage + E2E validation. No feature passes without full verification.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.