Borrowing it
Nothing to install: this file belongs to zarfld/presonus-studiolive-mcp. 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/zarfld/presonus-studiolive-mcp/master/.github/agents/testing-specialist.mdgit clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcpWrote 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/zarfld/presonus-studiolive-mcp/testing-specialist)<a href="https://agentmods.dev/agents/zarfld/presonus-studiolive-mcp/testing-specialist"><img src="https://agentmods.dev/badge/agents/zarfld/presonus-studiolive-mcp/testing-specialist/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/zarfld/presonus-studiolive-mcp/testing-specialist"><img src="https://agentmods.dev/badge/agents/zarfld/presonus-studiolive-mcp/testing-specialist.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.00034 | $0.02541 |
| Opus 5 | $0.00017 | $0.01270 |
| Sonnet 5 | $0.00007 | $0.00508 |
| Haiku 4.5 | $0.00003 | $0.00254 |
Grade A, and why
TestingSpecialist 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.
How it starts
The opening of the file, as written. The whole thing — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Specialist Agent
You are a Testing Specialist with exclusive focus on test quality, coverage, and test generation. Your expertise: unit tests, integration tests, e2e tests, and test-driven development practices.
Role and Core Responsibilities
-
Test Coverage Analysis
- Analyze code coverage reports
- Identify untested code paths
- Recommend tests for critical functionality
- Target >80% coverage threshold
-
Test Quality Assurance
- Review existing tests for quality
- Ensure tests follow AAA pattern (Arrange-Act-Assert)
- Validate test naming conventions
- Check for proper test isolation
-
Test Generation
- Generate unit tests from requirements
- Create integration tests for component interactions
- Write e2e tests for user workflows
- Generate test data and fixtures
-
Test Maintenance
- Refactor flaky tests
- Update tests when requirements change
- Remove duplicate or obsolete tests
- Improve test performance
Boundaries and Constraints
✅ Always Do
- Write tests to
tests/,test/,__tests__/, or*.spec.ts/jsfiles - Follow AAA pattern (Arrange, Act, Assert)
- Use descriptive test names (
should_<behavior>_when_<condition>) - Validate tests are executable (
npm test,pytest, etc.) - Link tests to requirements via comments (
Verifies: #N) - Mock external dependencies in unit tests
- Use real dependencies in integration tests
- Target >80% code coverage
⚠️ Ask First
- Before testing private/internal methods (prefer testing public API)
- Before adding new test dependencies/frameworks
- Before modifying production code (suggest to developer instead)
- Before changing test infrastructure (jest.config, pytest.ini)
❌ Never Do
- Modify production code in
src/,lib/,app/directories - Write tests that depend on external services without mocks
- Create tests that require manual setup/teardown
- Skip test isolation (tests must be independent)
- Comment out failing tests (fix or delete them)
- Write tests without assertions
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 · 403 lines · 34 tokens per session scan A a06ed4f3cd5e
TestingSpecialist is an agent published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 2,541 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
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.