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/armanzeroeight/fastagent-pluginsWrote 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/armanzeroeight/fastagent-plugins/test-strategist)<a href="https://agentmods.dev/agents/armanzeroeight/fastagent-plugins/test-strategist"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/test-strategist.svg" alt="Measured on agentmods" 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.00039 | $0.00883 |
| Opus 5 | $0.00019 | $0.00441 |
| Sonnet 5 | $0.00008 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00088 |
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 3d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Strategist
Strategic testing decisions and test planning guidance.
Decision Framework
Test Type Selection
Unit Tests - When to prioritize:
- Pure functions with clear inputs/outputs
- Business logic and calculations
- Utility functions and helpers
- New feature development
Integration Tests - When to prioritize:
- API endpoints and routes
- Database operations
- External service interactions
- Component integration points
End-to-End Tests - When to prioritize:
- Critical user workflows
- Multi-step processes
- UI interactions
- Cross-system functionality
Coverage Strategy
High Coverage Priority (aim for 80%+):
- Core business logic
- Payment and transaction code
- Security-critical functions
- Data transformation logic
Medium Coverage Priority (aim for 60%+):
- API endpoints
- Database queries
- Utility functions
- Configuration logic
Low Coverage Priority (aim for 40%+):
- UI components (focus on critical paths)
- Simple getters/setters
- Configuration files
- Type definitions
Skill Delegation
For coverage analysis: Delegate to test-coverage-analyzer skill
- Analyzes existing coverage
- Identifies gaps
- Recommends priority areas
For test data: Delegate to test-data-generator skill
- Creates fixtures
- Generates mock data
- Sets up test scenarios
Approach Selection
New Feature Development
- Start with unit tests for core logic
- Add integration tests for external interactions
- Consider e2e tests for critical workflows
- Aim for 70-80% coverage
Bug Fixes
- Write failing test that reproduces bug
- Fix the bug
- Verify test passes
- Add related edge case tests
Refactoring
- Ensure existing tests pass
- Add tests for uncovered areas
- Refactor with confidence
- Verify all tests still pass
Legacy Code
- Add characterization tests first
- Gradually increase coverage
- Focus on high-risk areas
- Refactor incrementally
Testing Patterns by Technology
JavaScript/TypeScript:
- Jest for unit/integration
- Vitest for Vite projects
- Playwright/Cypress for e2e
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.
- 3d ago First seen · 168 lines · 39 tokens per session scan A 622b7a59fa64
test-strategist is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 883 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-09-03.
Other agents, from other repositories
gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
e2e-runner
End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.