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 skills add san-npm/skills-ws --skill testing-strategygit clone --depth 1 https://github.com/san-npm/skills-wsWrote 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/san-npm/skills-ws/testing-strategy)<a href="https://agentmods.dev/skills/san-npm/skills-ws/testing-strategy"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/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.
<a href="https://agentmods.dev/skills/san-npm/skills-ws/testing-strategy"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/testing-strategy.svg" alt="Reviewed on agentmods" width="80" 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.00078 | $0.00535 |
| Opus 5 | $0.00039 | $0.00267 |
| Sonnet 5 | $0.00016 | $0.00107 |
| Haiku 4.5 | $0.00008 | $0.00053 |
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 5d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategy
Reference guide
Read only the references needed for the current request:
- Testing Pyramid: references/testing-pyramid.md
- Framework Selection: references/framework-selection.md
- TDD Workflow: references/tdd-workflow.md
- Mocking Patterns: references/mocking-patterns.md
- Test Fixtures & Factories: references/test-fixtures-factories.md
- Coverage Targets: references/coverage-targets.md
- CI Integration: references/ci-integration.md
- Flaky Test Management: references/flaky-test-management.md
- Visual Regression Testing: references/visual-regression-testing.md
- Contract Testing: references/contract-testing.md
- Test Data Management: references/test-data-management.md
- Snapshot Testing: references/snapshot-testing.md
- CI Test Parallelization: references/ci-test-parallelization.md
- Mutation Testing: references/mutation-testing.md
- Test Strategy & Governance: references/test-strategy-governance.md
- API Testing Patterns: references/api-testing-patterns.md
- Performance Testing: references/performance-testing.md
- Error Monitoring (Production): references/error-monitoring-production.md
- Logging: references/logging.md
- Observability Checklist: references/observability-checklist.md
What ships with it
21 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 203 B
- references/api-testing-patterns.md 3.1 KB
- references/ci-integration.md 1.0 KB
- references/ci-test-parallelization.md 3.4 KB
- references/contract-testing.md 2.6 KB
- references/coverage-targets.md 2.1 KB
- references/error-monitoring-production.md 1.6 KB
- references/flaky-test-management.md 566 B
- references/framework-selection.md 465 B
- references/logging.md 2.5 KB
- references/mocking-patterns.md 735 B
- references/mutation-testing.md 1.6 KB
- references/observability-checklist.md 1.5 KB
- references/performance-testing.md 3.9 KB
- references/snapshot-testing.md 1.8 KB
- references/tdd-workflow.md 410 B
- references/test-data-management.md 6.2 KB
- references/test-fixtures-factories.md 668 B
- references/test-strategy-governance.md 6.2 KB
- references/testing-pyramid.md 1.2 KB
- references/visual-regression-testing.md 2.6 KB
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.
- 5d ago First seen · 31 lines · 78 tokens per session scan A 5b70edeb3c33
testing-strategy is a skill published in the GitHub repository san-npm/skills-ws (2 stars, last pushed 5d ago), licensed MIT. It adds 78 tokens to every session and 535 once invoked, about $0.0004 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-07.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.