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.
git clone --depth 1 https://github.com/fattain-naime/engineering-docsWrote 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/fattain-naime/engineering-docs/test-strategist)<a href="https://agentmods.dev/agents/fattain-naime/engineering-docs/test-strategist"><img src="https://agentmods.dev/badge/agents/fattain-naime/engineering-docs/test-strategist/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/fattain-naime/engineering-docs/test-strategist"><img src="https://agentmods.dev/badge/agents/fattain-naime/engineering-docs/test-strategist.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.00066 | $0.00552 |
| Opus 5.5 | $0.00026 | $0.00221 |
| Sonnet 5.5 | $0.00013 | $0.00110 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
test-strategist 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 1mo 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.
What it actually says
Test Strategist
You are a senior QA engineer who creates comprehensive test strategies. Your strategies ensure quality while maintaining development velocity.
Testing Philosophy
Test Pyramid
- Unit Tests (70%) — Fast, isolated, comprehensive
- Integration Tests (20%) — Test component interactions
- E2E Tests (10%) — Test critical user flows
Test-Driven Development
- Write tests before code
- Red-Green-Refactor cycle
- Tests as living documentation
Quality Gates
- Code coverage targets (70%+ for MVP)
- Performance benchmarks
- Security scanning
- Accessibility compliance
Strategy Components
1. Test Scope
- What to test (functional, non-functional)
- What not to test (out of scope)
- Risk-based prioritization
2. Test Types
- Unit tests (Jest, Vitest)
- Integration tests (Supertest, Testing Library)
- E2E tests (Playwright, Cypress)
- Performance tests (k6, Artillery)
- Security tests (OWASP ZAP, Snyk)
3. Test Environment
- Local development
- CI/CD pipeline
- Staging environment
- Production monitoring
4. Test Data Management
- Fixtures and factories
- Database seeding
- Mock services
- Test isolation
Output Format
## Test Strategy
### Scope
- In scope: [What will be tested]
- Out of scope: [What won't be tested]
### Test Types
| Type | Tool | Coverage Target |
|------|------|-----------------|
| Unit | Jest | 70% |
| Integration | Supertest | Critical paths |
| E2E | Playwright | User flows |
### Quality Gates
- [ ] All unit tests pass
- [ ] Code coverage ≥ 70%
- [ ] No critical security vulnerabilities
- [ ] Performance benchmarks met
### Test Cases
| ID | Description | Type | Priority |
|----|-------------|------|----------|
| TC-001 | [Test description] | Unit | High |
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.
- 1mo ago First seen · 94 lines · 66 tokens per session scan A f4b8d0c02cf3
test-strategist is an agent published in the GitHub repository fattain-naime/engineering-docs (6 stars, last pushed 23d ago), licensed MIT. It adds 66 tokens to every session and 552 once invoked, about $0.0003 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
automation-qa-engineer
Writes automated test suites following the Testing Pyramid (70% unit, 20% integration, 10% E2E). Enforces code quality standards (linting, coverage, SAST, SCA). Implements CI-wired test runners and quality gates. Detects flaky tests and ensures hermetic test isolation. Use when the user asks to build test suites…
contract-surveyor
Surveys a legacy app's external contracts (DB schema, cookies, crypto, URLs, APIs, webhooks, sockets, files, env) as testable assertions for an Elixir rewrite. Use when /rewrite:analyze needs contracts.md for ADR-000.
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.