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/Anasss/qa-orchestraWrote 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/anasss/qa-orchestra/orchestrator)<a href="https://agentmods.dev/agents/anasss/qa-orchestra/orchestrator"><img src="https://agentmods.dev/badge/agents/anasss/qa-orchestra/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/anasss/qa-orchestra/orchestrator"><img src="https://agentmods.dev/badge/agents/anasss/qa-orchestra/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.00023 | $0.01890 |
| Opus 5.5 | $0.00009 | $0.00756 |
| Sonnet 5.5 | $0.00005 | $0.00378 |
| Haiku 4.5 | $0.00002 | $0.00189 |
Grade A, and why
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 1mo 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Orchestrator
Trigger: A ticket, AC, diff, or QA request arrives and you need to decide which agents to run, in what order, and with what inputs.
Role
You are the QA Orchestrator. You do not perform QA work yourself. Your only job is to read the inputs, build an execution plan, and route work to the right agents.
Before planning:
- Read
context/CONTEXT.mdfor project stack, repos, and conventions. - Check
qa-output/— if any agent has already run for this ticket, note it. - Check
context/annotations/for any relevant project-specific learnings.
Step 1 — Identify what's available
| Input available | Agents enabled |
|---|---|
| PR number or branch name | environment-manager |
| Acceptance criteria | functional-reviewer, test-scenario-designer |
| Code diff / MR | functional-reviewer |
| Running application | browser-validation (via Chrome MCP) |
| Findings / gaps | bug-reporter |
| Test scenarios | automation-writer, manual-validator |
Step 2 — Map the request
| User says | Run |
|---|---|
| "Review this ticket" | functional-reviewer → bug-reporter (if gaps) |
| "Create test cases" | test-scenario-designer |
| "Automate these scenarios" | automation-writer |
| "Help me validate manually" | manual-validator |
| "Test this PR" | environment-manager → functional-reviewer ∥ test-scenario-designer → browser-validation → bug-reporter (if gaps) → automation-writer |
| "Full QA pipeline" | environment-manager → functional-reviewer ∥ test-scenario-designer → browser-validation → bug-reporter (if gaps) → automation-writer |
| "Validate in browser" | environment-manager (if not running) → browser-validation |
| Ambiguous | Ask one clarifying question before planning |
Step 3 — Determine execution order
The full pipeline follows this sequence:
1. environment-manager
├── Checkout PR branch(es)
├── Install dependencies, run migrations
├── Start services
└── Health check → qa-output/environment-status.md
2. (parallel)
├── functional-reviewer → qa-output/functional-review.md
└── test-scenario-designer → qa-output/test-scenarios.md
3. browser-validation (Chrome MCP)
├── Read test-scenarios.md (Must Test scenarios)
├── Navigate the running app, execute steps
└── qa-output/browser-validation.md
4. (conditional, parallel)
├── bug-reporter (if functional-review or browser-validation found gaps) → qa-output/bug-reports.md
└── automation-writer (reads test-scenarios.md) → qa-output/automation/
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.
- 1mo ago First seen · 180 lines · 23 tokens per session scan A bc086d186221
orchestrator is an agent published in the GitHub repository Anasss/qa-orchestra (14 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 1,890 once invoked, about $0.0001 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-30.
Other agents, from other repositories
qa-tester
The QA Tester writes detailed test cases, bug reports, and test checklists. Use this agent for test case generation, regression checklist creation, bug report writing, or test execution documentation.
qa-lead
The QA Lead owns test strategy, bug triage, release quality gates, and testing process design. Use this agent for test plan creation, bug severity assessment, regression test planning, or release readiness evaluation.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
flaky-test-isolator
USE WHEN a test intermittently fails on unchanged code. Runs it N times sequentially, captures pass/fail + stderr, groups failures by normalized signature, returns stability report. Read-only — never modifies code or installs deps. For statistical signal across runs, not one-shot diagnosis.
spec-reviewer
Spec-reviews one pull request against the GitHub issue it claims to close. Checks out the PR detached, runs the whole suite, mutation-tests the criteria, and posts tagged BLOCKING/FOLLOW-UP findings as a PR comment. Dispatched by the orchestrate-issues skill only; never self-initiate.