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/HigorAlves/orcWrote 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/commands/higoralves/orc/qa)<a href="https://agentmods.dev/commands/higoralves/orc/qa"><img src="https://agentmods.dev/badge/commands/higoralves/orc/qa/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/commands/higoralves/orc/qa"><img src="https://agentmods.dev/badge/commands/higoralves/orc/qa.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.00053 | $0.02795 |
| Opus 5.5 | $0.00021 | $0.01118 |
| Sonnet 5.5 | $0.00011 | $0.00559 |
| Haiku 4.5 | $0.00005 | $0.00280 |
Grade A, and why
qa 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Bash(curl:*) How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:qa
Run a quality gate before opening a PR. Two modes:
- Code/CLI/library change — run tests, lint, type-check; verify with
orc:verification-before-completion; do a self-review withorc:caveman-review. No browser. - Web change — same as above PLUS browser-driven QA, with a driver chosen per run (the
orc:browser-qadriver gate): Playwright (Driver P, default — real tests plus a stitched, step-tagged video and traces), theagent-browserCLI via theorc-qa-validatoragent (Driver A, headless one-off walk), or the Claude-in-Chrome extension run inline in this session (Driver B — the user watches the test live in their own browser). Evidence is saved to.orc/<branch>/files/qa/either way.
Arguments
-
--auto[=guided|full]— autopilot level for this run (overridesinteraction_policy); ladder and hard-outward exemption inorc:gates§6. -
--target <name>— a named QA target from.orc/targets.json(orc:qa-targets):localprovisions the Docker env; a remote target (staging, preview) is probed and used as-is. Omitted ⇒ the Target gate asks.--web <url>remains as the ad-hoc remote shorthand. -
--web <url>— explicit URL of a running app (skips env provisioning AND the validator's boot path — you're saying it's already up). -
--no-web— force code-only mode even if web files were touched. -
--no-env— skip Docker env provisioning; the validator falls back to its legacy dev-script boot. -
--driver playwright|agent-browser|chrome— pick the browser driver up front and skip theorc:browser-qadriver gate.playwright= Playwright Test with the planner/generator/healer agents (tests committed undere2e/, stitched step-tagged video, traces).agent-browser= headless CLI viaorc-qa-validator(criterion-anchored annotated screenshots, WebM recording whenffmpegis installed, HAR, network mocking).chrome= Claude-in-Chrome extension, run inline so the user watches live in their real browser (real sessions/extensions, GIF recording). -
The remaining argument is the feature description (used to scope golden-path testing).
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 Changed · +8 lines 3f85073c66cc
- 13d ago Changed · +1 lines 73af96164bbb
- 1mo ago First seen · 138 lines · 53 tokens per session scan A 8418cca6fb7a
qa is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 2,795 once invoked, about $0.0002 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.
Other commands, from other repositories
e2e
Generate and run E2E tests with Playwright.
qa
A manual acceptance-testing command for checking a live product against Markdown scenarios. Acceptance testing checks whether a complete user task works, rather than testing individual pieces of code.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
playwright-setup
Verify Playwright CLI installation and create a .playwright/cli.config.json configuration file. Use when setting up browser automation, configuring Playwright, or user mentions "setup playwright", "configure browser testing", "install playwright".
browsertest
Run, create, debug, and maintain browser tests.
create-smoke-test.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.