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 thesongzhu/Friday --skill browser-qa-reportgit clone --depth 1 https://github.com/thesongzhu/FridayWrote 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/thesongzhu/friday/browser-qa-report)<a href="https://agentmods.dev/skills/thesongzhu/friday/browser-qa-report"><img src="https://agentmods.dev/badge/skills/thesongzhu/friday/browser-qa-report/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/thesongzhu/friday/browser-qa-report"><img src="https://agentmods.dev/badge/skills/thesongzhu/friday/browser-qa-report.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.00000 | $0.00070 |
| Opus 5.5 | $0.00000 | $0.00028 |
| Sonnet 5.5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
browser-qa-report 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 Report
Runs a read-only browser QA pass and returns evidence.
It captures:
- page status and title
- screenshot path and accessibility snapshot
- console, page, and request failures
Typical triggers:
qa this pagetest this app in the browsercapture a browser qa report
What ships with it
3 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.
- 1mo ago First seen · 16 lines · 0 tokens per session scan A d71337bcef25
browser-qa-report is a skill published in the GitHub repository thesongzhu/Friday (836 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 70 tokens. 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
browser-use
Drive a real browser to QA a running app. Screenshots, clicks, forms, evidence. Use when there is no Playwright suite, or when a human flow must be walked.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
startup-qa-bot-getting-started
A guided first conversation for a product-checking assistant. It helps define a safe test environment and choose an initial check, such as following a sign-up flow or comparing two versions.
startup-qa-bot-ops
A working procedure for checking a product in a clearly separated test environment. It maintains a page map, records observations, compares known page lists, and reports reproducible problems.
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.