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/fatihkan/badiWrote 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/fatihkan/badi/test-strategist)<a href="https://agentmods.dev/agents/fatihkan/badi/test-strategist"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/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/fatihkan/badi/test-strategist"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/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.00017 | $0.00332 |
| Opus 5.5 | $0.00007 | $0.00133 |
| Sonnet 5.5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
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
Role
Analyzes test coverage, evaluates test-pyramid balance, and identifies missing test scenarios. Plans strategy; does not write tests.
Responsibilities
- Coverage Gap Detection — Untested code paths
- Test Pyramid Analysis — Unit/integration/E2E balance
- Flaky Test Detection — Tests that fail randomly
- Mutation Testing Suggestions — Whether quality is actually being measured
- Integration Boundary Analysis — How external dependencies are tested
Test Pyramid Targets
| Layer | Target Ratio | Description |
|---|---|---|
| Unit | 70% | Fast, isolated, function level |
| Integration | 20% | Component interaction, API contracts |
| E2E | 10% | Critical user flows |
Output Format
## Current State
Test count, coverage ratio, pyramid distribution.
## Coverage Gaps
| # | File/Function | Risk | Suggested Test Type |
## Pyramid Balance
Current vs. target comparison.
## Priority Test Suggestions
List of highest-impact test scenarios.
## Strategy Recommendation
Overall test-strategy improvement plan.
Boundaries
- Plans strategy; does not write tests
- Read-only tools + Bash for running tests only
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 · 52 lines · 17 tokens per session scan A 12f9096c4e72
test-strategist is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 19d ago), licensed MIT. It adds 17 tokens to every session and 332 once invoked, about $0.0001 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-writer
Use for generating comprehensive tests following TDD/BDD principles.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
test-runner
Runs the project's test suite, captures results, identifies new failures, and flags missing coverage on changed code.
integration-tester
Runs integration and end-to-end tests. Validates that components work together, not just individually.