Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add victoraguilarsantamariadev/qa-explore/plugin install qa-exploreWrote 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/victoraguilarsantamariadev/qa-explore/qa-gate)<a href="https://agentmods.dev/skills/victoraguilarsantamariadev/qa-explore/qa-gate"><img src="https://agentmods.dev/badge/skills/victoraguilarsantamariadev/qa-explore/qa-gate/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/victoraguilarsantamariadev/qa-explore/qa-gate"><img src="https://agentmods.dev/badge/skills/victoraguilarsantamariadev/qa-explore/qa-gate.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.00153 | $0.01431 |
| Opus 5 | $0.00077 | $0.00715 |
| Sonnet 5 | $0.00031 | $0.00286 |
| Haiku 4.5 | $0.00015 | $0.00143 |
Grade A, and why
qa-gate 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 9d 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.
qa-gate
Top QA orgs don't just run tests — they own the ship decision. qa-gate is that decision, standardized: it takes the evidence the rest of the suite already gathered and turns it into a GO / NO-GO against a rubric you can read, version, and defend — the same way a release manager signs off.
signals in → explore findings (severity × confidence, verified?)
Step-0 deterministic suite (green? red?)
access-control findings · a11y violations · (visual drift · perf budget)
apply RUBRIC (deterministic, configurable) → count blockers, honour waivers
verdict OUT → GO ✅ / NO-GO ❌ + the exact blockers + risk summary + waiver audit trail
→ qa-signoff.md (the sign-off a human/CI can act on)
🔒 Why the verdict is deterministic
A gate that changes its mind run-to-run is not a gate. The GO/NO-GO is computed by rules over the signals — same inputs, same verdict, every time. The LLM is used ONLY to write the narrative (risk summary, wording), never to decide whether to ship. This is what makes it auditable and CI-safe.
The default release rubric (all configurable in gate)
A finding blocks the release when it is:
- severity ∈
blockOn(default["blocker","major"]), AND - confirmed — the Verify pass marked it
confirmed:true, or its confidence ishard-evidence(self-proving: a captured 2xx/leak/console error), AND - not waived (see below).
Plus these hard gates (each configurable):
requireStep0Green(default true): the Step-0 deterministic regression suite must be green. A red baseline = NO-GO (unless waived) — shipping on a red suite is how regressions escape.blockOnAccessControl(default true): any confirmed access-control / broken-authorization finding = NO-GO, regardless of the severity label. Security is not negotiable at the gate.a11yBlockOn(default["critical"]): axe-core violations at these impact levels block.- Optional
visualBlock/perfBudgetif you feed visual-regression / Lighthouse results.
What ships with it
1 file 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.
- 9d ago First seen · 61 lines · 153 tokens per session scan A ddbb73dab009
qa-gate is a skill published in the GitHub repository victoraguilarsantamariadev/qa-explore (2 stars, last pushed 1mo ago), licensed MIT. It adds 153 tokens to every session and 1,431 once invoked, about $0.0008 per session on Opus 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
generate-a11y-tests
Generates comprehensive Playwright accessibility tests with axe-core integration for any UI component or page. Use this skill to create automated accessibility regression tests that verify WCAG 2.1 Level AA compliance.\n\n \nContext: Developer has just completed building a login form component.\nuser: \"Generate…
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.
e2e-testing
End-to-end testing for Falcon Foundry apps using Playwright and @crowdstrike/foundry-playwright. TRIGGER when user asks to "add e2e tests", "add playwright tests", "write end-to-end tests", "test my app", or mentions "e2e", "playwright", or "end-to-end" in the context of testing a Foundry app. DO NOT TRIGGER during…
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…
e2e-reviewer
Use when reviewing Playwright or Cypress E2E specs, Page Objects (POM), PRs, pull requests, patches, diffs, or changed test files — asked to review tests, audit test quality, or find weak, flaky, or silently-passing tests; when tests pass CI but prove nothing or miss bugs; when auditing missing awaits, vacuous or…