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 d-o-hub/github-template-ai-agents --skill testing-strategygit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/d-o-hub/github-template-ai-agents/testing-strategy)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/testing-strategy"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/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/d-o-hub/github-template-ai-agents/testing-strategy"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/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.00073 | $0.01078 |
| Opus 5.5 | $0.00029 | $0.00431 |
| Sonnet 5.5 | $0.00015 | $0.00216 |
| Haiku 4.5 | $0.00007 | $0.00108 |
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategy
Design and implement comprehensive testing strategies with modern techniques.
When to Use
- User asks to plan test suites or choose testing approaches
- Need to decide between property-based, visual regression, load testing, etc.
- Even if they just say "how should we test this" or "what testing approach should we use"
Strategy Decision Tree
What are you testing?
├── Business logic / algorithms → Property-Based Testing
│ └── Tool: Hypothesis (Python), fast-check (JS)
├── UI appearance / visual state → Visual Regression
│ └── Tool: Playwright screenshots, Percy, Chromatic
├── Performance under load → Load & Stress Testing
│ └── Tool: Locust (Python), k6 (JS), JMeter (Java)
├── Test suite quality itself → Mutation Testing
│ └── Tool: Mutmut (Python), Stryker (JS/Java/C#)
└── End-to-end user flows → E2E Testing
└── Tool: Playwright, Cypress, Selenium
Strategy Reference
| Strategy | What It Catches | When To Use | Effort |
|---|---|---|---|
| Property-Based | Edge cases, boundary conditions | Algorithms, data transformations, parsers | Medium |
| Visual Regression | UI layout shifts, rendering bugs | Any visual component, responsive design | Low |
| Load & Stress | Performance bottlenecks, memory leaks | APIs, databases, critical paths | High |
| Mutation Testing | Weak assertions, missing test cases | Any code with existing unit tests | Medium |
| E2E | Integration bugs, user flow breaks | Critical user journeys, smoke tests | High |
Language-Specific Tools
| Language | Property-Based | Visual | Load | Mutation |
|---|---|---|---|---|
| Python | Hypothesis | Playwright | Locust | Mutmut |
| JavaScript | fast-check | Playwright/Percy | k6 | Stryker |
| Java | jqwik | Selenium | JMeter | PIT |
| C# | FsCheck | Playwright | NBomber | Stryker.NET |
Quality Gates
Integrate testing into CI/CD:
- Check mutation score thresholds (>80% target)
- Monitor Core Web Vitals in load tests (LCP < 2.5s)
- Auto-quarantine flaky tests after 3 consecutive failures
- Fail build if coverage drops on new code
What ships with it
3 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.
- 2d ago Changed · +1 lines 8b97b77ee542
- 18d ago Changed · -5 tokens per session 57086589dbd5
- 25d ago Changed · +6 lines 27bd986d9ba9
- 1mo ago First seen · 99 lines · 78 tokens per session scan A fb51039ee00a
testing-strategy is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,078 once invoked, about $0.0003 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-31.
Other skills, from other repositories
omh-agent-evaluation
This is a Hermes-native agent-evaluation workflow skill.
omh-verification-gate
This is an OMH verification-gate workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
debugging
Use this skill when something is broken and the cause is unknown — a failing test, a crash, an error message, wrong output, a regression, a hang, or behaviour that differs between environments — and it has to be found and fixed at the root. Also use it to build the failing proof for a suspected defect before fixing…
visual-regression
Setup visual regression testing with Storybook stories, configuration, and CI/CD workflows. Supports Chromatic, Percy, BackstopJS. Auto-invoke when user says "set up visual regression", "add Chromatic tests", "add screenshot testing", or "set up Percy".
Vizra ADK Evaluation Framework
Test and evaluate AI agents with automated evaluations, assertions, and LLM-as-a-Judge patterns.
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.