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 skills/data-wise/craft/test-strategistnpx skills add Data-Wise/craft --skill test-strategistgit clone --depth 1 https://github.com/Data-Wise/craftWrote 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/skills/data-wise/craft/test-strategist)<a href="https://agentmods.dev/skills/data-wise/craft/test-strategist"><img src="https://agentmods.dev/badge/skills/data-wise/craft/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 | $0.00063 | $0.00415 |
| Opus 5 | $0.00032 | $0.00208 |
| Sonnet 5 | $0.00013 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00042 |
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 Skill
Expert in test strategy, coverage optimization, and quality assurance.
When to Use
Use this skill when:
- Planning test strategy for new features
- Improving test coverage
- Debugging flaky or failing tests
- Optimizing test performance
- Setting up testing infrastructure
Capabilities
Test Strategy Design
- Unit, integration, and e2e test planning
- Test pyramid optimization
- Coverage target recommendations
- Test isolation strategies
Coverage Analysis
- Identify untested code paths
- Suggest high-value test cases
- Coverage metric interpretation
- Risk-based testing priorities
Test Quality
- Flaky test detection and fixes
- Test performance optimization
- Mock and fixture best practices
- Test maintainability improvements
Framework Expertise
- pytest, unittest (Python)
- Jest, Vitest, Mocha (JavaScript)
- testthat (R)
- go test (Go)
- cargo test (Rust)
Example Prompts
"Help me create a test strategy for our authentication module"
"Why is this test flaky and how do I fix it?"
"What tests should I add to improve coverage of the payment flow?"
"How do I structure integration tests for our API?"
"Suggest mocking strategies for external service dependencies"
Outputs
- Test plans with prioritized cases
- Coverage improvement recommendations
- Flaky test analysis and fixes
- Test refactoring suggestions
- Performance optimization tips
Integration
Works with:
/craft:test- Execute tests/craft:test --coverage- Coverage reports/craft:test debug- Debug failures/craft:ci:local- CI validation
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 · 77 lines · 63 tokens per session scan A dae20c9a9e24
test-strategist is a skill published in the GitHub repository Data-Wise/craft (4 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 415 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-09-03.
Other skills, from other repositories
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
testing-patterns
Redirect — testing-patterns was split into 5 focused sub-skills. Use when looking for testing-patterns, writing tests, or test automation. Redirects to testing-unit, testing-e2e, testing-integration, testing-llm, or testing-perf.
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
mandu-testing
Testing patterns for Mandu applications. Use when writing unit tests, integration tests, or E2E tests. Triggers on test, spec, Bun test, Playwright, or testing tasks.
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
nara-testing
Writing or modifying tests for a feature, Hono route, repository, Vue page, or CLI command.