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/fattain-naime/engineering-docs/test-strategistgit clone --depth 1 https://github.com/fattain-naime/engineering-docsWhat 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.00066 | $0.00552 |
| Opus 5 | $0.00033 | $0.00276 |
| Sonnet 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 2d 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.
- 2d 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 (4 stars, last pushed 17d ago), licensed MIT. It adds 66 tokens to every session and 552 once invoked, about $0.0003 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
exec-remote-slurm
Execute a TensorRT-LLM workload on a remote Slurm cluster via SSH. Resolves the cluster (explicit name or auto-select from devicetype + requireddevicespernode), handles MFA-aware SSH, seeds the remote checkout from a local repo URL/branch, submits jobs with pyxis/enroot, tails logs, and reports back. The orchestrator…
stripe-flow-reviewer
Use this agent when reviewing checkout, payment intent, or webhook handling code. Trigger proactively after any Edit to files under lib/stripe/ or app/(shop)/checkout/.
woo-regression-reviewer
WooCommerce regression-invariant review — Action Scheduler traps, meta equality and sync-on-read loops, template/theme overrides, broken-until-JS defaults, filter return-type variance, PHP coercion, migration legacy state, heuristic proxy predicates vs. store-configuration variance, removed-markup selector contracts…
board-verifier
Independent verifier for delivery-board tasks (haiku tier, fresh context). Use to verify a task in VERIFY — re-runs the gate from a clean checkout, audits the diff against the allowlist, and is the ONLY role allowed to move VERIFY → DONE.
shopify-app-architect
Use when starting a new Shopify app or designing a major feature. Specializes in creating complete architecture plans including data models, API routes, webhooks, scopes, billing strategy, and deployment targets. Route here for architecture approval workflows.
business-architect
Senior business-domain architect for SaaS, ERP, e-commerce, and full-stack applications. Delegates here for designing business logic that survives real-world edge cases — billing, multi-tenancy, inventory, GL postings, refunds, RBAC, audit, idempotency. Knows how Stripe, Linear, NetSuite, Shopify, and similar solve…