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 juspay/xyne-spaces --skill browser-qa-deliverygit clone --depth 1 https://github.com/juspay/xyne-spacesWrote 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/juspay/xyne-spaces/browser-qa-delivery)<a href="https://agentmods.dev/skills/juspay/xyne-spaces/browser-qa-delivery"><img src="https://agentmods.dev/badge/skills/juspay/xyne-spaces/browser-qa-delivery/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/juspay/xyne-spaces/browser-qa-delivery"><img src="https://agentmods.dev/badge/skills/juspay/xyne-spaces/browser-qa-delivery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.00198 |
| Opus 5.5 | $0.00012 | $0.00079 |
| Sonnet 5.5 | $0.00006 | $0.00040 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
browser-qa-delivery 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.
What it actually says
Browser QA and delivery
Before delivery:
- Serve or open the artifact inside the writable sandbox.
- Navigate with the sandbox Playwright tools and capture a desktop screenshot.
- Inspect the semantic snapshot, browser console, and failed network requests.
- Test the primary interaction and keyboard focus path.
- Repeat at a narrow mobile viewport. Check overflow and content order.
- Fix defects and rerun the affected checks.
- Ensure the delivered document contains no inspector code, secrets, local-only URLs, missing assets, or development placeholders.
- Call
sandbox-deliver-fileswith the exact HTML file that passed QA.
Do not paste the full source into chat. The attachment is the product; the final text should only identify what was delivered and any unavoidable limitation.
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 · 22 lines · 30 tokens per session scan A 93a7e576b567
browser-qa-delivery is a skill published in the GitHub repository juspay/xyne-spaces (822 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 198 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 skills, from other repositories
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
playwright-pro
Production-grade Playwright testing skill for E2E suites, flaky test diagnosis, browser automation, migration from Cypress/Selenium, CI integration, visual checks, and regression validation.
cypress-ops
Cypress end-to-end and component testing operations - selector/retry-ability strategy, cy.intercept network stubbing, cy.session auth, component vs e2e, flake diagnosis, CI, Test Replay. Use for: cypress, e2e test, component test, cy.get, cy.intercept, cy.session, data-cy, data-test, retry-ability, flake, flaky test…
playwright-ops
Playwright end-to-end testing operations - selectors, fixtures, network mocking, auth, parallelism, CI, visual regression, flake hunting. Use for: playwright, e2e test, end-to-end testing, browser test, getByRole, page object, storageState, trace viewer, flaky test, test sharding, visual regression, toHaveScreenshot…
webapp-testing
Exercise and verify a local web application through Playwright, including user flows and rendered behaviour. Use when testing a running local app rather than issuing an isolated browser command. For ad hoc automation, use $playwright-cli.
clay-agent-browser
Test websites and browse together with the user in Clay's live Browser panel. Use for browser testing, checking UI changes, opening pages, filling forms, clicking controls, screenshots, and watching an agent work in Clay. Prefer this skill over independent agent-browser or Playwright sessions when sharedbrowser is…