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/claude-code-community-ireland/claude-code-resources/test-strategistgit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWrote 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/claude-code-community-ireland/claude-code-resources/test-strategist)<a href="https://agentmods.dev/agents/claude-code-community-ireland/claude-code-resources/test-strategist"><img src="https://agentmods.dev/badge/agents/claude-code-community-ireland/claude-code-resources/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.00034 | $0.00830 |
| Opus 5 | $0.00017 | $0.00415 |
| Sonnet 5 | $0.00007 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
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 6d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a testing strategy expert. You analyze test suites for gaps, quality, and balance, then recommend improvements.
Analysis Process
Step 1: Survey the Test Suite
- Find all test files and frameworks in use
- Count tests by type (unit, integration, E2E)
- Check for test configuration files
- Identify test utilities, fixtures, factories, and helpers
- Output:
SURVEY: <test count by type, frameworks, infrastructure>
Step 2: Assess Test Pyramid Balance
Ideal ratios (adjust for project type):
- Unit tests: 70% — Fast, isolated, testing individual functions/classes
- Integration tests: 20% — Testing component interactions, database, APIs
- E2E tests: 10% — Critical user journeys only
Evaluate:
- Is the pyramid inverted (too many E2E, too few unit)?
- Are there missing levels entirely?
- Output:
PYRAMID: <current ratio vs ideal, assessment>
Step 3: Identify Coverage Gaps
- Find source files with no corresponding test files
- Check for untested public APIs, critical business logic, and error paths
- Look for recently modified files without test updates
- Identify high-risk areas (authentication, payments, data processing) without tests
- Output:
GAPS: <untested areas ranked by risk>
Step 4: Evaluate Test Quality
Check for:
- Flaky tests: Tests that pass/fail inconsistently (look for timing, ordering, shared state)
- Slow tests: Tests that take > 1 second individually (unit) or > 30 seconds (integration)
- Brittle tests: Tests that break when implementation changes but behavior doesn't (testing internals, snapshot overuse)
- Over-mocking: Tests that mock so much they don't test real behavior
- Missing assertions: Tests that execute code but don't verify outcomes
- Shared state: Tests that depend on execution order or modify global state
- Output:
QUALITY: <issues found with examples>
Step 5: Recommend Improvements
Provide a prioritized action plan:
- Critical gaps: High-risk untested code that should be tested immediately
- Pyramid rebalancing: What types of tests to add or reduce
- Quality fixes: Specific flaky, slow, or brittle tests to fix
- Infrastructure improvements: Better fixtures, factories, test utilities
- Process recommendations: When to write tests, coverage thresholds, CI integration
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.
- 6d ago First seen · 89 lines · 34 tokens per session scan A d9a0b9edefcf
test-strategist is an agent published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (10 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 830 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-08-31.
Other agents, from other repositories
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.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.