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 Omar-Obando/qwen-orchestrator --skill testing-strategygit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/testing-strategy)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/testing-strategy"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/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/omar-obando/qwen-orchestrator/testing-strategy"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/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.00059 | $0.02795 |
| Opus 5 | $0.00030 | $0.01398 |
| Sonnet 5 | $0.00012 | $0.00559 |
| Haiku 4.5 | $0.00006 | $0.00280 |
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 — 465 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategy Skill — Comprehensive Test Coverage
Overview
This skill provides comprehensive guidance for designing and implementing testing strategies for software projects. It covers the testing pyramid, coverage thresholds, CI/CD integration, and test automation best practices. Based on software testing certification standards and industry best practices.
When to Use
Use this skill when:
- Designing test strategy for new projects
- Setting up CI/CD quality gates
- Defining test coverage requirements
- Implementing unit, integration, and E2E tests
- Optimizing test execution time
- Improving test reliability
- Creating testing pyramid architecture
- Setting coverage thresholds for different layers
- Implementing test data management strategies
- Building test automation frameworks
- Creating test reporting and dashboards
- Implementing flaky test detection
- Setting up parallel test execution
- Building test environment management
- Implementing test coverage reporting
- Creating test quality gates
- Setting up test performance baselines
- Implementing test result analysis
- Building test maintenance strategies
- Creating test documentation standards
- Implementing test security scanning
- Setting up test monitoring and alerting
- Building test optimization strategies
- Creating test team structure and roles
Do NOT use this skill when:
- Writing specific test cases (use TDD workflow skill)
- Debugging specific test failures (use debugging skill)
- Writing production code (use implementer agent or specific framework skill)
- Designing database schema (use database design skill)
Testing Pyramid
┌─────────────────┐
│ E2E Tests │ ~5-10% of tests
│ (Integration) │ Slow, comprehensive
├─────────────────┤
│ Integration │ ~20-30% of tests
│ Tests │ Medium, module interactions
├─────────────────┤
│ Unit Tests │ ~60-75% of tests
│ │ Fast, isolated logic
└─────────────────┘
What ships with it
1 file 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.
- 5d ago First seen · 465 lines · 59 tokens per session scan A 4d0c98d42e4e
testing-strategy is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 2,795 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-09-03.
Other skills, from other repositories
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
prd-auto-test-loop
A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.