Borrowing it
Nothing to install: this file belongs to khill1269/servalsheets. 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/main/.claude/agents/testing-specialist.mdgit clone --depth 1 https://github.com/khill1269/servalsheetsWrote 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/testing-specialist)<a href="https://agentmods.dev/agents/khill1269/servalsheets/testing-specialist"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/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/testing-specialist"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/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.03321 |
| Opus 5.5 | $0.00024 | $0.01328 |
| Sonnet 5.5 | $0.00012 | $0.00664 |
| Haiku 4.5 | $0.00006 | $0.00332 |
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 — 476 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 (threads mode, CI=4 workers, local=8 workers)
- Coverage: v8 provider — 50% lines/functions, 30% branches
- Mutation testing: Stryker (9 critical files, threshold 60%)
- Property-based: fast-check (8 test files)
- Chaos: Failure injection (4 test files)
- Live API: Real Google Sheets integration (40 test files, 3 tiers)
ServalSheets Test Pyramid (613 total test files):
| Tier | Dir | Files | Command |
|---|---|---|---|
| Audit | tests/audit/ |
5 | npm run audit:coverage/perf/memory |
| Contract | tests/contracts/ |
41 | npm run test:fast (included) |
| Handler | tests/handlers/ |
73 | npm run test:fast (included) |
| Services | tests/services/ |
81 | npm run test:services |
| Integration | tests/integration/ |
20 | npm run test:integration |
| Compliance | tests/compliance/ |
15 | npm run test:compliance |
| Property | tests/property/ |
8 | npm run test:run tests/property |
| Chaos | tests/chaos/ |
4 | npm run test:run tests/chaos |
| Packages | tests/packages/ |
38 | npm run test:mcp-http-task-contract |
| Snapshots | tests/snapshots/ |
1 | npm run test:snapshots |
| Live API | tests/live-api/ |
40 | npm run test:live:smoke/nightly |
| E2E | tests/e2e/ |
10 | npm run test:run tests/e2e |
| Security | tests/security/ |
8 | npm run test:run tests/security |
Live API tiers:
npm run test:live:smoke # Quick subset (~10 min, smoke config)
npm run test:live:nightly # Full suite (all 40 files, nightly config)
npm run test:live:optimizations # Performance optimization tests
npm run test:live:full # Alias for nightly
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
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 · 476 lines · 59 tokens per session scan A 8e44e28ae518
testing-specialist is an agent published in the GitHub repository khill1269/servalsheets (0 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 3,321 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
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
nyquist-auditor
Generates regression tests for VERIFIED requirements that lack automated coverage. Spawned during F5.5 NYQUIST phase of /foundry:start when run with --nyquist.