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.
npx skills add HigorAlves/orc --skill browser-qagit 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/skills/higoralves/orc/browser-qa)<a href="https://agentmods.dev/skills/higoralves/orc/browser-qa"><img src="https://agentmods.dev/badge/skills/higoralves/orc/browser-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/skills/higoralves/orc/browser-qa"><img src="https://agentmods.dev/badge/skills/higoralves/orc/browser-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.00042 | $0.01323 |
| Opus 5.5 | $0.00017 | $0.00529 |
| Sonnet 5.5 | $0.00008 | $0.00265 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
browser-qa 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 3d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser QA
The single source of truth for driving browser QA — /orc:qa and /orc:flow both execute this protocol instead of restating it. Inputs from the caller: the feature description, the state dir, --driver/--web/--no-env flags when given, and (workspace mode) the web-surface repo + siblings.
Step 0 — Resolve the target
Invoke orc:qa-targets: --target / --web / settled decision / the Target gate. Result: a target name (plus a --base-url override when one applies) and guard. The resolved JSON is never produced here — the engine resolves it inline in the command that consumes it (orc:qa-targets iron rule). Remote target ⇒ probe; unreachable ⇒ 🛑 Escalation — target unreachable, stop.
Step 1 — Provision or attach the environment (local target only)
Skip for remote targets and under --no-env. Check orc-docker-env is-ready $(orc-docker-env state-path "$ORC_STATE_DIR" <sanitized-branch>):
ready→ attach; echo the reuse line (project, appUrl, "reused").- otherwise → dispatch
orc-env-provisionerviaTask(repoPath = the worktree; workspace mode addsrepos[],webSurfaceRepo, plan path). Onfallback: re-print the agent's ⚠️ callout and continue. Onfailed: re-print the 🛑 callout andAskUserQuestion— retry / retry--fresh/ continue with--no-envlegacy boot / abort QA.
Record <appUrl> as the --base-url override for the local target (the engine resolves inline). The environment stays up after QA — the "QA partial → fix → re-run" loop attaches in seconds. Teardown belongs to /orc:cleanup. Init ${ORC_STATE_DIR}/<sanitized-branch>/files/qa/; in workspace mode, cross-repo integration evidence goes there while per-repo QA stays at <repoPath>/.orc/<branch>/files/qa/.
Step 1b — Choose the driver
If --driver was passed or the session has a settled driver decision, use it silently. Otherwise print the Gate headline, then AskUserQuestion (re-runs keep the same driver unless the user asks to switch):
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · -22 lines · -22 tokens per session eb1bac1d1881
- 16d ago Changed · +11 lines · -8 tokens per session 67cf958ef9e9
- 1mo ago First seen · 72 lines · 72 tokens per session scan A b222f9f64335
browser-qa is a skill published in the GitHub repository HigorAlves/orc (7 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,323 once invoked, about $0.0002 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-31.
Other skills, from other repositories
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
e2e-panther-playwright
Write end-to-end tests with Symfony Panther 2.4 for browser automation or Playwright for complex scenarios.
playwright-expert
Use when writing or fixing E2E tests in a Playwright project - playwright.config.ts, .spec.ts files under tests/ or e2e/, @playwright/test imports - or right after implementing a frontend/backend change that needs an end-to-end proof. Writes and extends TypeScript E2E suites as the QA gate for feature and bug-fix…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
chrome-verify-checks
Use when verifying a chrome-extension/ change before reporting done. The canonical 7-check list (build → Service Worker vm.createContext compat → manifest sanity → per-site content-script DOM contract → message-passing trace → test suite → manual-load checklist) + verdict rules. chrome-extension/ is a strong-guard…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.