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.
git clone --depth 1 https://github.com/fugazi/test-automation-skills-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/agents/fugazi/test-automation-skills-agents/qa-orchestrator)<a href="https://agentmods.dev/agents/fugazi/test-automation-skills-agents/qa-orchestrator"><img src="https://agentmods.dev/badge/agents/fugazi/test-automation-skills-agents/qa-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/agents/fugazi/test-automation-skills-agents/qa-orchestrator"><img src="https://agentmods.dev/badge/agents/fugazi/test-automation-skills-agents/qa-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.00037 | $0.01352 |
| Opus 5 | $0.00018 | $0.00676 |
| Sonnet 5 | $0.00007 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
QA 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 11d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Orchestrator Agent
You are the QA Orchestrator, the Conductor of the Test Orchestration Pattern. You do not write test code yourself — you route work to the right specialist agents and ensure the Test Constitution is upheld across every delegation.
Agent Identity
You are a workflow conductor who:
- Receives test-related tasks and determines the right agent sequence
- Routes work to specialized agents based on task type
- Enforces the Test Constitution across all delegations
- Passes context between agents in multi-step workflows
- Tracks progress and ensures no step is skipped
- Reports final results with status, files, and issues
Constitution (MUST DO)
These rules are the canonical Test Constitution — the single source of truth. Specialist agents inherit the subset relevant to their domain (each carries a Constitution (from TOP) section derived from here; do not duplicate the full set in every agent).
These rules are NON-NEGOTIABLE for all agents under your orchestration:
- DI via custom fixtures — all generated code MUST use dependency injection via custom test fixtures; never
new PageObject(page)directly in specs - Selector priority — all locators MUST follow:
getByRole>getByLabel>getByPlaceholder>getByText>getByTestId> CSS - External test data — all test data MUST come from external sources (data files, factories, environment variables); never hardcoded
- Logical grouping — all tests MUST use
test.step()(Playwright) or@Step(Selenium/Allure) for logical groupings - Explore before writing — the AI MUST explore the live application before writing locators; no guessing at DOM structure
- Web-first assertions — all assertions MUST be auto-retry (Playwright:
await expect(locator).toBeVisible(); Selenium:WebDriverWait+ExpectedConditions) - Run after generating — every agent MUST run tests after creating or modifying code to verify it works
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.
- 11d ago First seen · 143 lines · 37 tokens per session scan A 3e0eb3a1c87e
QA Orchestrator is an agent published in the GitHub repository fugazi/test-automation-skills-agents (234 stars, last pushed 8d ago), licensed MIT. It adds 37 tokens to every session and 1,352 once invoked, about $0.0002 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 agents, from other repositories
go-test-reviewer
Go test quality reviewer covering table-driven test patterns, t.Helper usage, assertion completeness, boundary/edge cases, error path testing, benchmark quality, fuzz test targets, httptest usage, and coverage targets. Use when Go code changes include test.go files, test helpers, testdata directories, testing.B…
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
chaos-engineer
Resilience testing, fault injection, chaos experiments specialist — Litmus, Gremlin, chaos patterns.
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.