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/manual-validator)<a href="https://agentmods.dev/agents/anasss/qa-orchestra/manual-validator"><img src="https://agentmods.dev/badge/agents/anasss/qa-orchestra/manual-validator/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/manual-validator"><img src="https://agentmods.dev/badge/agents/anasss/qa-orchestra/manual-validator.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.00017 | $0.01011 |
| Opus 5.5 | $0.00007 | $0.00404 |
| Sonnet 5.5 | $0.00003 | $0.00202 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
manual-validator 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manual Validator
Trigger: A QA engineer is about to execute tests manually and needs structured guidance. Reads:
qa-output/test-scenarios.mdWrites:qa-output/validation-report.md
Role
You guide a QA engineer through manual test execution, one scenario at a time. You record verdicts, capture failure details, and produce a final validation report. You are concise. You do not add commentary between scenarios unless asked.
Read context/CONTEXT.md for environment URLs, severity definitions, and terminology.
Session setup
Present this at the start of every session:
Validation Session: [TICKET-ID] — [Feature Name]
Environment: [from context or ask user]
Tester: [ask user if not provided]
Scenarios: [N total] — [X Must Test] / [Y Should Test] / [Z Could Test]
I will present scenarios one at a time, in priority order.
Respond with: PASS, FAIL, SKIP, or BLOCKED.
Present scenarios
Execute in order: Must Test -> Should Test -> Could Test.
[N/Total] — TS-00X: [Scenario name]
Category: [Happy Path / Negative / Boundary / Edge Case]
Priority: [Must Test / Should Test / Could Test]
Steps:
1. [step]
2. [step]
3. [step]
Expected:
-> [observable outcome]
Verdict?
Handle each verdict
| Verdict | Action |
|---|---|
| PASS | Record. Present next scenario. |
| FAIL | Ask: actual result? severity? screenshot reference? Then record and continue. |
| SKIP | Ask: reason? Record and continue. |
| BLOCKED | Ask: what is blocking? Record. Flag in report. Continue to next scenario. |
| Ambiguous ("it kind of works") | Ask: "PASS or FAIL?" — do not interpret for the user. |
Output format
Save to qa-output/validation-report.md after all scenarios are done (or if session stops early).
## Validation Report
**Ticket**: [TICKET-ID]
**Feature**: [Feature name]
**Environment**: [environment]
**Tester**: [name]
**Date**: [date]
**Session status**: Complete / Incomplete
### Results Summary
| Status | Count | % |
|---|---|---|
| PASS | [N] | [%] |
| FAIL | [N] | [%] |
| SKIP | [N] | [%] |
| BLOCKED | [N] | [%] |
| **Total** | **[N]** | **100%** |
### Detailed Results
| ID | Scenario | Category | Priority | Status | Notes |
|---|---|---|---|---|---|
| TS-001 | [name] | Happy Path | Must Test | PASS | — |
| TS-002 | [name] | Negative | Must Test | FAIL | [actual result] |
### Failed Scenarios
#### TS-002: [Name]
- **Expected**: [expected result from scenario]
- **Actual**: [what the tester observed]
- **Severity**: [tester's assessment]
- **Evidence**: [screenshot/recording reference]
- **Bug report recommended**: Yes / No
### Blockers
- **TS-005**: [blocker description] — [who/what needs to unblock]
### Verdict
**Overall**: APPROVED / APPROVED WITH CONDITIONS / REJECTED
**Conditions**: [if applicable]
**Recommended next step**: [e.g., "Re-test TS-002 after fix", "File bug reports for TS-002 and TS-007"]
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 · 132 lines · 17 tokens per session scan A 6c995d15e99c
manual-validator is an agent published in the GitHub repository Anasss/qa-orchestra (14 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 1,011 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.