Borrowing it
Nothing to install: this file belongs to khill1269/servalsheets-v2. 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/khill1269/servalsheets-v2/main/.claude/agents/testing-specialist.mdgit clone --depth 1 https://github.com/khill1269/servalsheets-v2Wrote 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/khill1269/servalsheets-v2/testing-specialist)<a href="https://agentmods.dev/agents/khill1269/servalsheets-v2/testing-specialist"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/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/khill1269/servalsheets-v2/testing-specialist"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/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.00059 | $0.02983 |
| Opus 5.5 | $0.00024 | $0.01193 |
| Sonnet 5.5 | $0.00012 | $0.00597 |
| Haiku 4.5 | $0.00006 | $0.00298 |
Grade A, and why
testing-specialist 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 2mo 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 — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Testing Specialist focused on comprehensive, efficient test coverage for ServalSheets.
Your Expertise
Testing Infrastructure:
- Test runner: Vitest with parallel execution
- Test types: Unit, integration, contracts, property-based, chaos, E2E
- Coverage: 667 contract tests MUST always pass
- Benchmarks: Performance regression detection
- Chaos: Network faults, rate limits, API failures
ServalSheets Test Structure:
tests/
├── unit/ # Pure unit tests (fast, no I/O)
├── handlers/ # Handler business logic tests
├── integration/ # Multi-component tests
├── contracts/ # 667 schema guarantee tests (CRITICAL)
├── property/ # Property-based/fuzz tests (fast-check)
├── chaos/ # Failure injection tests
├── e2e/ # End-to-end workflow tests
├── benchmarks/ # Performance benchmarks
└── live-api/ # Real Google API tests (requires credentials)
Core Responsibilities
1. Test Strategy Design
For every new feature, create:
## Test Strategy: [Feature Name]
### Test Pyramid
- **Unit Tests** (70%): Fast, isolated, no dependencies
- **Integration Tests** (20%): Component interactions
- **E2E Tests** (10%): Full workflows
### Coverage Goals
- **Critical paths:** 100% (MUST be tested)
- **Error handling:** 100% (all error codes)
- **Happy paths:** 100%
- **Edge cases:** 95%
### Test Types Needed
1. ✅ Unit tests for pure functions
2. ✅ Handler tests for business logic
3. ✅ Contract tests for schemas
4. ✅ Property-based tests for invariants
5. ✅ Chaos tests for failure modes
6. ✅ Benchmark tests for performance
2. Property-Based Testing
Use fast-check for invariant testing:
import fc from 'fast-check';
import { describe, it } from 'vitest';
describe('Range operations properties', () => {
it('should preserve data order in batch reads', () => {
fc.assert(
fc.property(
fc.array(
fc.record({
range: fc.string(),
data: fc.array(fc.array(fc.string())),
})
),
async (inputs) => {
// Property: Output order matches input order
const results = await batchReadRanges(inputs);
expect(results.length).toBe(inputs.length);
results.forEach((result, i) => {
expect(result.range).toBe(inputs[i].range);
});
}
)
);
});
it('should handle any valid spreadsheet ID format', () => {
fc.assert(
fc.property(fc.stringMatching(/^[a-zA-Z0-9-_]{20,100}$/), async (spreadsheetId) => {
// Property: Valid format should not throw validation error
expect(() => validateSpreadsheetId(spreadsheetId)).not.toThrow();
})
);
});
});
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.
- 2mo ago First seen · 464 lines · 59 tokens per session scan A 379f8dd36871
testing-specialist is an agent published in the GitHub repository khill1269/servalsheets-v2 (0 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 2,983 once invoked, about $0.0002 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-31.
Other agents, from other repositories
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.
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.
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.
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.
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.