Borrowing it
Nothing to install: this file belongs to sw23/fp-conv. 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/sw23/fp-conv/main/.github/skills/browser-testing/SKILL.mdgit clone --depth 1 https://github.com/sw23/fp-convWrote 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/sw23/fp-conv/browser-testing)<a href="https://agentmods.dev/skills/sw23/fp-conv/browser-testing"><img src="https://agentmods.dev/badge/skills/sw23/fp-conv/browser-testing/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/sw23/fp-conv/browser-testing"><img src="https://agentmods.dev/badge/skills/sw23/fp-conv/browser-testing.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.00060 | $0.02272 |
| Opus 5.5 | $0.00024 | $0.00909 |
| Sonnet 5.5 | $0.00012 | $0.00454 |
| Haiku 4.5 | $0.00006 | $0.00227 |
Grade B, and why
browser-testing scanned grade B with 1 finding 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 7d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
2. **Enable browser tools in chat**: Open the Tools picker in the chat input and enable all tools under Built-in > Browser How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser UI Testing
Test the floating-point conversion calculator in an actual browser using VS Code's browser agent tools. Supports three testing modes: visual verification, interaction testing, and conversion validation.
Prerequisites
- Enable browser tools: Set
workbench.browser.enableChatToolstotruein VS Code settings - Enable browser tools in chat: Open the Tools picker in the chat input and enable all tools under Built-in > Browser
- Use
#tool:openBrowserPageto openindex.htmlfrom the workspace root as afile://URL (no local server needed — the built-in browser loads local files and scripts correctly). Construct the URL from the workspace path, e.g.file://${workspaceFolder}/index.html
Reference Files
- UI element map — All DOM selectors, element IDs, button data attributes
- Test vectors — Known-good encode/decode/conversion values for validation
Procedure A — Visual Verification
Verify the page renders correctly and all sections are present.
Steps
- Open the page with
#tool:openBrowserPage - Take an initial screenshot with
#tool:screenshotPage— verify:- Header displays "Floating Point Conversion Calculator"
- Subtitle "Convert between floating point, integer, and custom formats" is visible
- All four main sections are visible: Input Format, Input Value, Output Format, Output Value
- Format preset buttons are rendered in groups (IEEE 754, ML, OCP, Integer)
- Binary bit display shows clickable checkboxes
- About section is present at the bottom
- Use
#tool:readPageto confirm page text content includes:- All format button labels: FP64, FP32, FP16, BF16, TF32, FP8 E5M2, FP8 E4M3, FP6 E3M2, FP6 E2M3, FP4 E2M1
- All integer format labels: INT32, UINT32, INT16, UINT16, INT8, UINT8, INT4, UINT4
- Value preset labels: 0, 1, Max Norm, Min Norm, Max Sub, Min Sub, +Inf, -Inf, NaN, 1s
- Rounding mode options: Nearest Ties to Even, Ties Away, Toward Zero, Toward +Infinity, Toward -Infinity
- NaN mode options: Canonical quiet NaN, Preserve sign and payload
- Verify the default initial state matches:
- Input format: FP16 (total bits = 16)
- Output format: BF16 (total bits = 16)
- Decimal value: 3.140625
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.
- 7d ago Changed · +1 lines 15f419a31010
- 2mo ago First seen · 189 lines · 60 tokens per session scan B ba907dded3a2
browser-testing is a skill published in the GitHub repository sw23/fp-conv (7 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 2,272 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
blazemeter-recorders
Comprehensive guide for BlazeMeter Recorders, including Chrome Extension and Proxy Recorder. Use when working with recorders for (1) Recording tests with Chrome Extension, (2) Creating and using Proxy Recorder, (3) Configuring browsers and devices for proxy recording, (4) Setting port ranges for proxy recorder, or any…
playwright
Browser automation, web scraping, E2E testing, and visual regression with Playwright. Covers 30+ patterns: login flows, form testing, responsive design checks, broken link validation, API mocking, data extraction, PDF generation, accessibility audits (axe-core), performance budgets (Lighthouse), visual diffing…
gstack-qa
QA lead with real browser testing. Tests your app, finds bugs, fixes them with atomic commits, generates regression tests. Use when the user says "QA", "test this", "find bugs", "exploratory test", "QA this", or "test the app".
qa-use
E2E testing and browser automation with qa-use CLI. Use when the user needs to run tests, verify features, automate browser interactions, or debug test failures.
blazemeter-private-locations
Comprehensive guide for BlazeMeter Private Locations, including Radar Agent, installation (Docker, Kubernetes, Helm), configuration, management, and troubleshooting. Use when working with Private Locations for (1) Installing agents (Docker, Kubernetes, Helm Chart), (2) Configuring Radar Agent for API Monitoring, (3)…
blazemeter-functional-testing
Comprehensive guide for BlazeMeter Functional Testing, including GUI Functional Tests, API Tests (deprecated), Action Library, and debugging. Use when working with Functional Testing for (1) Creating GUI Functional Tests (YAML, Java IDE, Python IDE), (2) Managing Functional Tests (duplicate, delete, move, rename), (3)…