agentmods.dev

orc-qa-validator

orc-qa-validator is an agent for Claude Code from HigorAlves/orc. It costs 67 tokens per session (1,487 once invoked), scanned A, original, MIT.

A browser-testing role that opens a running web application, uses it like a real person, and records what happens. It checks the main user journey and unusual cases rather than only running code-level tests.

In plain words
What is it for?
Use it to test a web app in a real browser, capture annotated screenshots and a recording, inspect accessibility results, and collect console and network evidence.
Why use it?
It provides evidence of whether the application works in practice and makes failures easier for others to verify.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Part of the orc plugin — 88 skills, 30 commands, 14 agents, 6 hooks shipped together

not rated 7repo +1 changed today A scan 67 tokens original MIT

Good fit Use it to test a web app in a real browser, capture annotated screenshots and a recording, inspect accessibility results, and collect console and network evidence.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/higoralves/orc/orc-qa-validator
View source ↗ HigorAlves/orc orc.novacstack.com
Install

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.

Clone the repo
git clone --depth 1 https://github.com/HigorAlves/orc

Made for: Claude Code.

Or install orc, the plugin that ships this one along with the rest of its 88 skills, 30 commands, 14 agents, 6 hooks.

Wrote 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.

agentmods badge for orc-qa-validator

README.md
[![agentmods](https://agentmods.dev/badge/agents/higoralves/orc/orc-qa-validator/github.svg)](https://agentmods.dev/agents/higoralves/orc/orc-qa-validator)
Your own site
<a href="https://agentmods.dev/agents/higoralves/orc/orc-qa-validator"><img src="https://agentmods.dev/badge/agents/higoralves/orc/orc-qa-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.

agentmods 80×15 button for orc-qa-validator

Your own site · 80×15
<a href="https://agentmods.dev/agents/higoralves/orc/orc-qa-validator"><img src="https://agentmods.dev/badge/agents/higoralves/orc/orc-qa-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,487 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.01487
Opus 5.5 $0.00027 $0.00595
Sonnet 5.5 $0.00013 $0.00297
Haiku 4.5 $0.00007 $0.00149

Measured today against content hash a94f2023b792, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orc-qa-validator scanned grade A with 1 finding 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 today.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

tools: Read, Write, Edit, Glob, Grep, Skill, Bash(curl:*), Bash(node:*), Bash(npm:*), Bash(pnpm:*), Bash(agent-browser:*), Bash(npx agent-browser:*), Bash(command -v:*), Bash(ffmpeg:*)
orc/agents/orc-qa-validator.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You drive a real browser via the agent-browser CLI to QA a web app. You open the app, click the buttons, watch what happens, and record what you saw with evidence anyone can verify. You are not a unit-test runner and not a code reviewer.

You are the agent-browser driver of /orc:qa. When the user picks the Claude-in-Chrome driver, QA runs inline and you are not dispatched.

Pre-flight

  1. Follow the preloaded orc:agent-browser skill; it is your entry point.
  2. Run agent-browser --version. If missing, run npm install -g agent-browser && agent-browser install.
  3. If the install fails, stop and surface it. Never fake QA.
  4. Run agent-browser skills get core and prefer its command shapes over this file.
  5. For a desktop app or exploratory QA, also load electron or dogfood the same way.

Inputs

  • Project context: docs/agents/project-context.md when present (binding rules).
  • The changed feature, described.
  • appUrl, serviceEndpoints, envStatePath from a provisioned environment (the usual case).
  • Only without an environment: a --web URL or legacy boot instructions.
  • The target directory .orc/<sanitized-branch>/files/qa/ (<qa-dir> below).
  • The acceptance criteria: each slice's acceptance list, tagged with slice id and index. They are your rubric.
  • isVisual: whether the change touches a rendered surface. When true, the recording is required.

Workspace mode adds repo, repoPath, siblingRepos, and optionally crossRepoContract. Walk an integration golden path that exercises the contract. Verify sibling traffic through serviceEndpoints in the HAR; never touch sibling repos. Cross-repo evidence goes to <workspaceRoot>/.orc/<branch>/files/qa/; repo-local evidence stays in <repoPath>/.orc/<branch>/files/qa/.

Workflow

Command recipes for every step: orc:agent-browser → references/QA-RECIPES.md. The steps.md template: references/STEPS-TEMPLATE.md.

⚠️ Caution

Never run docker, never start sibling repos, never tear the environment down. The provisioner owns infra. Never re-boot after a failed probe (steps 1–3).

Read the full file on GitHub · 97 lines

Changes

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.

  1. today Changed · +2 lines a94f2023b792
  2. 3d ago Changed · -164 lines · -43 tokens per session 8c2dffe6da72
  3. 16d ago Changed fcbb07298844
  4. 1mo ago First seen · 259 lines · 110 tokens per session scan A 0397ee81ca19

Subscribe to this mod's changes

orc-qa-validator is an agent published in the GitHub repository HigorAlves/orc (7 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 1,487 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Browser automationClaude CodeE2E testingTestingagentic-codingai-agentsanthropicclaudeclaude-code-plugin
Related

Other agents, from other repositories

qa-tester

The QA Tester of the aSPARK team. Use in the Review phase (/demo-day) to test the running application hands-on in a real browser: verify every acceptance criterion from the spec, explore beyond the happy path, check console and network, and file reproducible bugs. Requires a browser integration (Claude in Chrome…

a-lottes/aSPARK · 79 tokens

chrome-verify

Verifies a chrome-extension/ change before it is reported done. Checks Service Worker (Manifest v3) compatibility with vm.createContext, manifest-permissions integrity, content-script DOM contract per target site, and message-passing between popup ↔ service worker ↔ content script. Use after any change in…

jhlee0409/omni-harness-kit · 118 tokens

gan-evaluator

GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.

23ag1/completely · 32 tokens

gan-evaluator

GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.

affaan-m/ECC · 32 tokens

e2e-test-specialist

Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.

travisjneuman/.claude · 67 tokens

e2e-runner

End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.

vibeeval/vibecosystem · 69 tokens