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 ArieGoldkin/ai-agent-hub --skill testing-strategy-buildergit clone --depth 1 https://github.com/ArieGoldkin/ai-agent-hubWrote 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/ariegoldkin/ai-agent-hub/testing-strategy-builder)<a href="https://agentmods.dev/skills/ariegoldkin/ai-agent-hub/testing-strategy-builder"><img src="https://agentmods.dev/badge/skills/ariegoldkin/ai-agent-hub/testing-strategy-builder.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.1 | $0.00053 | $0.03370 |
| Opus 5 | $0.00026 | $0.01685 |
| Sonnet 5 | $0.00011 | $0.00674 |
| Haiku 4.5 | $0.00005 | $0.00337 |
Grade A, and why
testing-strategy-builder 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.
How it starts
The opening of the file, as written. The whole thing — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategy Builder
Overview
This skill provides comprehensive guidance for building effective testing strategies that ensure software quality, reliability, and maintainability. Whether starting from scratch or improving existing test coverage, this framework helps teams design robust testing approaches.
When to use this skill:
- Planning testing strategy for new projects or features
- Improving test coverage in existing codebases
- Establishing quality gates and coverage targets
- Designing test automation architecture
- Creating test plans and test cases
- Choosing appropriate testing tools and frameworks
- Implementing continuous testing in CI/CD pipelines
Bundled Resources:
references/code-examples.md- Detailed testing code examplestemplates/test-plan-template.md- Comprehensive test plan templatetemplates/test-case-template.md- Test case documentation templatechecklists/test-coverage-checklist.md- Coverage verification checklist
Required Tools
This skill references the following testing tools. Not all are required - the skill will recommend appropriate tools based on your project.
JavaScript/TypeScript Testing
-
Jest: Most popular testing framework
- Install:
npm install --save-dev jest @types/jest - Config:
npx jest --init
- Install:
-
Vitest: Vite-native testing framework
- Install:
npm install --save-dev vitest - Config: Add to vite.config.ts
- Install:
-
Playwright: End-to-end testing
- Install:
npm install --save-dev @playwright/test - Setup:
npx playwright install
- Install:
-
k6: Performance testing
- Install (macOS):
brew install k6 - Install (Linux): Download from k6.io
- Command:
k6 run script.js
- Install (macOS):
Python Testing
-
pytest: Standard Python testing framework
- Install:
pip install pytest - Command:
pytest
- Install:
-
pytest-cov: Coverage reporting
- Install:
pip install pytest-cov - Command:
pytest --cov=.
- Install:
-
Locust: Performance testing
- Install:
pip install locust - Command:
locust -f locustfile.py
- Install:
What ships with it
4 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.
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 · 485 lines · 53 tokens per session scan A 732021cab483
testing-strategy-builder is a skill published in the GitHub repository ArieGoldkin/ai-agent-hub (11 stars, last pushed 9mo ago), licensed MIT. It adds 53 tokens to every session and 3,370 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-08-30.
Other skills, from other repositories
test-generator
Generate comprehensive unit, integration, and end-to-end tests. Use when adding test coverage, writing tests for new features, or improving existing test suites.
accessibility-testing
Skill "accessibility-testing" from vibeeval/vibecosystem, covering accessibility testing, axe-core setup, jest-axe (unit / component tests), playwright-axe (e2e) and cypress-axe.
frontend-testing
Scaffold and advise on frontend testing for production readiness, mapped to the Front-End-Checklist Testing category (13 rules). Defines a testing pyramid (unit, integration, E2E, visual, a11y, cross-browser, real-device, perf-budget, mutation, error-monitoring, coverage, mocking, contract) and emits copy-pasteable…
testing-guide
A testing guide covering common testing levels, including unit, integration, system, and end-to-end testing. It also supports ISTQB and industry testing-pyramid approaches.
react-testing-workflows
Testing strategy and execution for React applications. Covers Vitest configuration, React Testing Library patterns, custom hook testing, Playwright E2E, Storybook stories and play functions, and coverage reporting. Keywords: test, vitest, testing library, playwright, storybook, coverage, unit test, integration test…
testing-strategy
Follow the testing pyramid — more unit tests, fewer integration tests, even fewer e2e tests.