Borrowing it
Nothing to install: this file belongs to aiblueprinthq/ai-blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aiblueprinthq/ai-blueprint/main/.agents/skills/browser-tests/SKILL.mdgit clone --depth 1 https://github.com/aiblueprinthq/ai-blueprintWrote 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/aiblueprinthq/ai-blueprint/browser-tests)<a href="https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/browser-tests"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/browser-tests/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/aiblueprinthq/ai-blueprint/browser-tests"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/browser-tests.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.00054 | $0.01217 |
| Opus 5 | $0.00027 | $0.00609 |
| Sonnet 5 | $0.00011 | $0.00243 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
browser-tests 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 6d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
browser-tests - set up repeatable browser verification
Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.
First action: Before project inspection, preflight, or any other tool call,
publish running to blueprint/.state/run.json using the dashboard activity
contract in AGENTS.md.
This is an explicit optional setup command. It creates a project-owned browser test path that later Feature, Implement, Check, and Continuous runs can reuse. It does not replace live browser inspection, install during another workflow command, or make browser testing mandatory for every Blueprint project.
Input
No argument is required. A named runner, browser, application surface, or flow is a preference to verify against the real project.
Step 1 - inspect the project
Read enough files to identify the actual browser surface and existing setup:
AGENTS.md, especially Commands and any Verify command- package or language manifests, lockfiles, workspaces, and runtime versions
- existing browser, integration, and end-to-end test configs and files
- build, dev, preview, extension-build, and test commands
- relevant CI workflows and ignore rules
blueprint/context/coding-standards.md- Git branch and worktree state
Do not assume Node.js, npm, a web server, or a blank test setup. Do not install dependencies or edit files during inspection.
Step 2 - choose the smallest useful harness
Reuse a working browser runner already established by the project. For a compatible JavaScript or TypeScript web app or browser extension with no runner, prefer Playwright Test. If the stack or executable surface is unclear, stop and ask instead of inventing a framework.
Choose one representative smoke path through a real project surface. It must prove the harness can launch the app and observe behavior, not merely assert that a static fixture exists. Keep authentication state, profiles, secrets, generated reports, traces, videos, and screenshots out of Git unless the project already has a deliberate safe convention.
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.
- 6d ago Changed · +2 lines · -27 tokens per session 3320f35c08ec
- 10d ago First seen · 132 lines · 81 tokens per session scan A 911a9e7b7ec8
browser-tests is a skill published in the GitHub repository aiblueprinthq/ai-blueprint (384 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,217 once invoked, about $0.0003 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-30.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
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.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…