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 agentmods add skills/sw23/fp-conv/browser-testingnpx skills add sw23/fp-conv --skill browser-testinggit clone --depth 1 https://github.com/sw23/fp-convWhat 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 | $0.00060 | $0.02254 |
| Opus 5 | $0.00030 | $0.01127 |
| Sonnet 5 | $0.00012 | $0.00451 |
| Haiku 4.5 | $0.00006 | $0.00225 |
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 2d 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 — 189 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
- 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.
- 2d 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 (5 stars, last pushed 6d ago), licensed MIT. It adds 60 tokens to every session and 2,254 once invoked, about $0.0003 per session on Opus 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
browse
Fast headless browser for QA testing and site dogfooding. (gstack).
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
e2e-deployment-skill
Use this deployment skill to verify shared skills load during Playwright startup.
launch
Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. Use when working on VS Code itself and you want to interact with the running workbench, automate chat or UI flows, test…
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.