What is workflow-test-strategy?

A workflow for evaluating or redesigning a project's test suite, the automated checks that verify code behavior. It covers test structure, speed, flakiness, coverage, framework changes, and maintenance cost.

Use it to audit or rework test infrastructure, migrate test frameworks, establish a testing strategy, or manage tests generated at scale.

A large or unreliable test suite can slow development and make failures hard to trust. This workflow helps decide whether the testing setup is helping or hurting the project.

workflow-test-strategy — Skill for Claude Code by saemihemma

Install

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.

Any agent

npx skills add saemihemma/lead-producer-oss --skill workflow-test-strategy

Clone the repo

git clone --depth 1 https://github.com/saemihemma/lead-producer-oss

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-test-strategy/github.svg)](https://agentmods.dev/skills/saemihemma/lead-producer-oss/workflow-test-strategy)

Your own site

<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/workflow-test-strategy"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-test-strategy/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/workflow-test-strategy"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-test-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 570 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00036	$0.00570
Opus 5	$0.00018	$0.00285
Sonnet 5	$0.00007	$0.00114
Haiku 4.5	$0.00004	$0.00057

Measured 8d ago against content hash 0ce51e54ed49, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

workflow-test-strategy 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 8d 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.

.claude/skills/workflow-test-strategy/SKILL.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Strategy Workflow

Purpose

Audit, redesign, or establish test infrastructure at the project level. Owns the macro question: "Is our test suite an asset or a liability, and what do we do about it?"

Use When

Test suite is large, slow, flaky, or structurally unsound
Migrating test frameworks or rearchitecting test infrastructure
Establishing test strategy from scratch on an existing codebase
AI agents are generating tests at scale and quality is degrading
Test maintenance cost is outpacing value

Do NOT Use When

Writing tests for a single feature (use workflow-test-driven-development)
Reviewing test coverage for a specific PR (use role-qa-engineer)
Root-cause debugging a test failure (use workflow-systematic-debugging)

Composition

role-qa-engineer (domain owner): test strategy, coverage architecture, risk-based prioritization
role-software-architect: test infrastructure boundaries, framework selection, CI integration shape
role-principal-software-engineer: test code quality, maintainability, redundancy

Workflow

Audit current state: suite size, run time, flake rate, coverage shape, framework age, AI-generated test ratio
Identify structural problems: redundancy, weak assertions, missing layers (unit/integration/e2e imbalance), isolation failures, slow feedback loops
Design target state: test architecture that protects critical behavior with minimum maintenance cost
Plan migration: phased approach, what to delete first, what to rewrite, what to keep, framework changes
Execute with TDD discipline: route implementation slices through workflow-test-driven-development

Default Output

TEST STRATEGY REPORT
====================
Current State: suite size, run time, flake rate, coverage shape, framework
Structural Problems: redundancy, weak layers, isolation failures, maintenance cost
Target State: test architecture, framework, layer balance, CI integration
Migration Plan: phases, deletion targets, rewrite priorities, risk
Verdict: investment justified / defer / partial overhaul

Read the full file on GitHub · 50 lines

Changes

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.

8d ago First seen · 50 lines · 36 tokens per session scan A 0ce51e54ed49

Subscribe to this mod's changes

workflow-test-strategy is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 570 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

workflow-test-strategy