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/drafthq/draft/testing-strategynpx skills add drafthq/draft --skill testing-strategygit clone --depth 1 https://github.com/drafthq/draftWhat 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.00038 | $0.01688 |
| Opus 5 | $0.00019 | $0.00844 |
| Sonnet 5 | $0.00008 | $0.00338 |
| Haiku 4.5 | $0.00004 | $0.00169 |
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 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.
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
-
Identify component types:
- APIs (REST, GraphQL, gRPC)
- Data pipelines (ETL, streaming)
- Frontend (React, Vue, etc.)
- Infrastructure (Terraform, K8s configs)
- Libraries/SDKs
- CLI tools
-
Discover existing tests:
find . -name "*test*" -o -name "*spec*" | head -50Identify: test frameworks, test directories, existing coverage config, test runners.
-
Assess current coverage: Check for existing coverage reports or configuration:
ls coverage/ .nyc_output/ htmlcov/ .coverage 2>/dev/null -
Read project context:
draft/tech-stack.md— Test frameworks, testing conventionsdraft/workflow.md— TDD preferences (strict/flexible/none)draft/.ai-context.md— INVARIANTS section (critical paths), module boundaries, concurrency modeldraft/guardrails.md— Anti-patterns that need test coveragedraft/product.md— Critical user flows that demand E2E tests
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 · 204 lines · 38 tokens per session scan A e78a17ad9bac
testing-strategy is a skill published in the GitHub repository drafthq/draft (40 stars, last pushed 14d ago), licensed MIT. It adds 38 tokens to every session and 1,688 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-30.
Other skills, from other repositories
test-driven-development
在实现任何功能或修复 bug 时使用，在编写实现代码之前.
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.