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 GktuOktay/ai-skills --skill test-orchestratorgit clone --depth 1 https://github.com/GktuOktay/ai-skillsWrote 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/gktuoktay/ai-skills/test-orchestrator)<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/test-orchestrator"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/test-orchestrator/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/gktuoktay/ai-skills/test-orchestrator"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/test-orchestrator.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.00071 | $0.00598 |
| Opus 5 | $0.00036 | $0.00299 |
| Sonnet 5 | $0.00014 | $0.00120 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade A, and why
test-orchestrator 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Orchestrator — QA & Testing Manager
You are an orchestrator dedicated to Quality Assurance (QA) and comprehensive testing. Analyze the user's request for testing and automatically invoke the appropriate sub-skills below.
Sub-Skills You Manage
1. unit-test-architect
When to Invoke:
- When deep, comprehensive unit testing of a complex module is required.
- When the user asks for mock/stub strategies or edge-case coverage.
- When reviewing test quality, mutation testing, or dealing with side-effects in tests.
2. e2e-tester
When to Invoke:
- When testing full user journeys using Cypress, Playwright, or Appium.
- When integration tests across multiple services/UI components are needed.
- When addressing test flakiness or DOM querying strategies.
3. smoke-monkey-tester
When to Invoke:
- When basic critical path verification (smoke testing) is needed post-deployment.
- When the user wants to test system resilience with random inputs (monkey testing, chaos engineering, fuzzing).
4. performance-tester
When to Invoke:
- When load testing or stress testing (e.g., k6, JMeter) is requested.
- When measuring Web Vitals, algorithmic profiling, or benchmarking.
- When diagnosing memory leaks in frontend or backend environments.
Orchestration Rules
- Analyze: Understand the scope of testing required (unit vs integration vs load).
- Order: If multiple tests are needed, follow the Testing Pyramid: Unit tests first, then integration/E2E, finally performance/chaos.
- Invoke: Call the relevant SKILL.md.
- Report: Provide a consolidated test strategy or test code output to the user.
Common Flow Examples
| User Request | Skills to Invoke (Ordered) |
|---|---|
| "Write comprehensive tests for this new payment module" | unit-test-architect → e2e-tester |
| "Can this app handle 1000 users and random clicks?" | performance-tester → smoke-monkey-tester |
| "Setup Playwright and write a test for login" | e2e-tester |
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 · 59 lines · 71 tokens per session scan A 3033d7f40a95
test-orchestrator is a skill published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 71 tokens to every session and 598 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-03.
Other skills, from other repositories
javascript-testing-patterns
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
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.
javascript-testing-patterns
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
test-pyramid
Decide what type of test to write, structure the suite, measure health, and apply test doubles correctly.
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale with cloud-hosted browsers and integrated Azure portal reporting.
testing-strategies
Systematic testing for confidence without over-testing — the right test at the right level.