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 test-automation-architecturegit 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/test-automation-architecture)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/test-automation-architecture"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/test-automation-architecture/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/test-automation-architecture"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/test-automation-architecture.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.00055 | $0.02367 |
| Opus 5 | $0.00028 | $0.01184 |
| Sonnet 5 | $0.00011 | $0.00473 |
| Haiku 4.5 | $0.00006 | $0.00237 |
Grade A, and why
test-automation-architecture 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 7d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Automation Architecture Skill — QA Engineer
Overview
This skill provides comprehensive guidance for designing and implementing test automation frameworks. It covers page object patterns, test reporting, parallel execution, test data management, and test infrastructure following CTFL-TA and ISTQB Advanced Level certifications.
When to Use
Use this skill when:
- Designing test automation frameworks
- Implementing page object patterns
- Creating test reporting and dashboards
- Managing parallel test execution
- Setting up test data management
- Designing test infrastructure
- Implementing test framework best practices
- Creating test libraries and utilities
- Setting up CI/CD integration
- Designing test environment management
- Implementing test result analysis
- Creating test metrics and KPIs
- Designing test coverage reporting
- Implementing test flakiness reduction
- Setting up test monitoring
- Designing test data privacy
- Implementing test version control
- Creating test documentation
- Designing test failure analysis
- Implementing test performance optimization
- Setting up test orchestration
- Designing test scalability
- Creating test maintainability strategies
- Implementing test quality gates
Do NOT use this skill when:
- Writing application business logic (use domain-driven skill)
- Designing database schemas (use database-design skill)
- Writing API endpoint specifications (use api-design skill)
- Performing security audits (use security-auditor skill)
- Writing SQL queries (use sql-best-practices skill)
- Designing multi-page website layouts (use design-system skill)
- Analyzing deployment configurations (use deployment skill)
- Writing documentation (use documentation-best-practices skill)
Test Framework Architecture
Layered Architecture
┌─────────────────────────────────────────────────────────────┐
│ Test Framework Architecture │
├─────────────────────────────────────────────────────────────┤
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Test Layer (Tests) │ │
│ │ - Feature tests │ │
│ │ - Integration tests │ │
│ │ - Unit tests │ │
│ └──────────────────────────────────────────────────────┘ │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Support Layer (Utilities) │ │
│ │ - Test data builders │ │
│ │ - API clients │ │
│ │ - Database helpers │ │
│ └──────────────────────────────────────────────────────┘ │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Framework Layer (Base Classes) │ │
│ │ - Page objects │ │
│ │ - Test base classes │ │
│ │ - Assertions │ │
│ └──────────────────────────────────────────────────────┘ │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Tool Layer (Test Runner) │ │
│ │ - Test runner (Jest, Mocha, Pytest) │ │
│ │ - Reporting (Allure, HTML report) │ │
│ │ - CI/CD integration │ │
│ └──────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────┘
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.
- 7d ago First seen · 306 lines · 55 tokens per session scan A 5c22581e6cf9
test-automation-architecture is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 2,367 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
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline...
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.