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 CodeInfinity1/Stram --skill live-browser-testinggit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/live-browser-testing)<a href="https://agentmods.dev/skills/codeinfinity1/stram/live-browser-testing"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/live-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/codeinfinity1/stram/live-browser-testing"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/live-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.00034 | $0.00720 |
| Opus 5.5 | $0.00014 | $0.00288 |
| Sonnet 5.5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
live-browser-testing 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Live Browser Testing
Purpose
Run real browser checks for local or remote web apps using Stram-owned Playwright-backed tools. This skill is inspired by webapp testing practices, but execution stays inside Stram's native browser tool surface.
When To Use
Use for frontend smoke tests, local app QA, login-free flows, responsive checks, forms, screenshots, console-visible behavior, downloads, PDF export, and verifying that a UI change actually renders.
Inputs And Evidence
- Target URL, expected screen, viewport needs, and user flow.
browser_live_statusreadiness.- Live session ID, observed element IDs, page URL/title/text, screenshot or artifact paths.
- Test result, blocker, or approval status for state-changing actions.
Tool Map
browser_live_statusbrowser_live_openbrowser_live_navigatebrowser_live_observebrowser_live_backbrowser_live_forwardbrowser_live_reloadbrowser_live_query_selectorbrowser_live_htmlbrowser_live_page_searchbrowser_live_find_elementsbrowser_live_extractbrowser_live_dropdown_optionsbrowser_live_select_optionbrowser_live_clickbrowser_live_hoverbrowser_live_click_coordinatesbrowser_live_dragbrowser_live_drag_coordinatesbrowser_live_typebrowser_live_fill_formbrowser_live_scrollbrowser_live_scroll_to_textbrowser_live_resizebrowser_live_press_keybrowser_live_upload_filebrowser_live_downloadbrowser_live_save_pdfbrowser_live_evaluate_jsbrowser_live_waitbrowser_live_screenshotbrowser_live_tabsbrowser_live_new_tabbrowser_live_switch_tabbrowser_live_close_tabbrowser_live_close
Workflow
- Check live browser readiness when setup is uncertain.
- Open the target URL and immediately observe the page.
- Use observed element IDs for clicks and typing; avoid stale coordinates.
- Take one state-changing action, then observe again.
- Capture screenshots for visual claims or regression evidence.
- Report verified behavior, blockers, and any untested assumptions.
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 · 98 lines · 34 tokens per session scan A 3e0c2cf7c5c3
live-browser-testing is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 720 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-31.
Other skills, from other repositories
browser-qa-delivery
Validate a Design Studio HTML artifact in the sandbox browser, fix rendering and runtime defects, then deliver exactly the tested file.
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.