agentmods.dev

testing-strategy

testing-strategy is a skill for Claude Code from drafthq/draft. It costs 38 tokens per session (1,688 once invoked), scanned A, original, MIT.

A testing-planning guide for choosing test types, setting realistic coverage goals, and matching tests to a project's architecture. TDD, or test-driven development, is a practice of writing tests as part of the development cycle.

In plain words
What is it for?
Use it to create a project-wide or feature-specific testing strategy and test plan. It can guide decisions about unit, integration, and end-to-end tests before implementation.
Why use it?
It prevents test plans that ignore the existing codebase, test setup, integration checks, or end-to-end behaviour. It also helps avoid treating 100% code coverage as a sensible goal for every project.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the draft plugin — 33 skills shipped together

not rated 40repo 11d ago A scan SkillSpector: pass 38 tokens original MIT

Good fit Use it to create a project-wide or feature-specific testing strategy and test plan. It can guide decisions about unit, integration, and end-to-end tests before implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/drafthq/draft/testing-strategy
View source ↗ drafthq/draft getdraft.dev
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 drafthq/draft --skill testing-strategy
Clone the repo
git clone --depth 1 https://github.com/drafthq/draft

Made for: Claude Code.

Or install draft, the plugin that ships this one along with the rest of its 33 skills.

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.

agentmods badge for testing-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/drafthq/draft/testing-strategy/github.svg)](https://agentmods.dev/skills/drafthq/draft/testing-strategy)
Your own site
<a href="https://agentmods.dev/skills/drafthq/draft/testing-strategy"><img src="https://agentmods.dev/badge/skills/drafthq/draft/testing-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.

agentmods 80×15 button for testing-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/drafthq/draft/testing-strategy"><img src="https://agentmods.dev/badge/skills/drafthq/draft/testing-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,688 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01688
Opus 5.5 $0.00015 $0.00675
Sonnet 5.5 $0.00008 $0.00338
Haiku 4.5 $0.00004 $0.00169

Measured 1mo ago against content hash e78a17ad9bac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

skills/testing-strategy/SKILL.md · 204 lines

How it starts

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

Testing Strategy

You are designing a testing strategy and test plan for this project or track.

Red Flags — STOP if you're

  • Writing a strategy without understanding the codebase
  • Setting unrealistic coverage targets (100% is rarely appropriate)
  • Focusing only on unit tests and ignoring integration/E2E
  • Ignoring existing test infrastructure and conventions
  • Not considering the testing pyramid for this project's architecture

A good testing strategy matches the architecture. Not every project needs the same pyramid.

Pre-Check

0. Capture Git Context

Before starting, capture the current git state:

git branch --show-current # Current branch name
git rev-parse --short HEAD # Current commit hash

Store this for the report header. The strategy is scoped to this specific branch/commit.

1. Verify Draft Context

ls draft/ 2>/dev/null

If draft/ doesn't exist, this skill can still run standalone with reduced context.

2. Load Draft Context (if available)

Read and follow the base procedure in core/shared/draft-context-loading.md.

Step 1: Parse Arguments

  • /draft:testing-strategy — Project-wide strategy (default if no active track)
  • /draft:testing-strategy track <id> — Track-scoped strategy
  • /draft:testing-strategy module <name> — Module-scoped strategy

Step 2: Analyze Codebase

  1. Identify component types:

    • APIs (REST, GraphQL, gRPC)
    • Data pipelines (ETL, streaming)
    • Frontend (React, Vue, etc.)
    • Infrastructure (Terraform, K8s configs)
    • Libraries/SDKs
    • CLI tools

  2. Discover existing tests:

    find . -name "*test*" -o -name "*spec*" | head -50

    Identify: test frameworks, test directories, existing coverage config, test runners.

  3. Assess current coverage: Check for existing coverage reports or configuration:

    ls coverage/ .nyc_output/ htmlcov/ .coverage 2>/dev/null

  4. Read project context:

    • draft/tech-stack.md — Test frameworks, testing conventions
    • draft/workflow.md — TDD preferences (strict/flexible/none)
    • draft/.ai-context.md — INVARIANTS section (critical paths), module boundaries, concurrency model
    • draft/guardrails.md — Anti-patterns that need test coverage
    • draft/product.md — Critical user flows that demand E2E tests

Read the full file on GitHub · 204 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.

  1. 1mo ago First seen · 204 lines · 38 tokens per session scan A e78a17ad9bac

Subscribe to this mod's changes

testing-strategy is a skill published in the GitHub repository drafthq/draft (40 stars, last pushed 11d ago), licensed MIT. It adds 38 tokens to every session and 1,688 once invoked, about $0.0002 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-30.

Claude CodeCode reviewPlanningTDDTestingai-code-reviewai-codingcopilotcursor
Related

Other skills, from other repositories

gentle-ai-bench

Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.

Gentleman-Programming/gentle-ai · 49 tokens

go-testing

Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.

Gentleman-Programming/gentle-ai · 26 tokens

refactor

You are the Refactor Specialist, a rigorous code quality engineer who improves code structure, maintainability, and performance while preserving behavior. You never break working code - you make it better.

samibs/skillfoundry · 6 tokens

refactoring-patterns

Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", or "decompose conditional". Also trigger when cleaning up legacy code…

KunanonJ/ai-skills-hub · 120 tokens

confidence-based-strictness

Use when the complexity or unfamiliarity of a task should increase guardrail enforcement. Scales verification depth based on how confident the system is in the correctness of the generated code.

Vimalk0703/shipworthy · 41 tokens

gentle-ai-collab-perfect

Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…

Gentleman-Programming/gentle-ai · 106 tokens