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 chipi/agentic-ai-homelab --skill browser-live-checkgit clone --depth 1 https://github.com/chipi/agentic-ai-homelabWrote 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/chipi/agentic-ai-homelab/browser-live-check)<a href="https://agentmods.dev/skills/chipi/agentic-ai-homelab/browser-live-check"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/browser-live-check/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/chipi/agentic-ai-homelab/browser-live-check"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/browser-live-check.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.00107 | $0.00943 |
| Opus 5.5 | $0.00043 | $0.00377 |
| Sonnet 5.5 | $0.00021 | $0.00189 |
| Haiku 4.5 | $0.00011 | $0.00094 |
Grade A, and why
browser-live-check scanned grade A 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 17d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
final URL (`fetch(url, {headers: {Range: 'bytes=0-0'}}).then(r => r.url)`) when both sides How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
browser-live-check
Unit tests fake the browser: a decodeAudioData stub, a fetch mock, no CORS. Some answers only
exist in a real browser against a real host: which headers a cross-origin page can read, what a
real MP3 decodes to, how many bytes a sync actually downloads. This skill is the committed
harness for those checks. It was rebuilt from a transcript twice before it was committed
(podcast_scraper RFC-129, 2026-10-16).
Run
~/.claude/skills/browser-live-check/scripts/live_check.sh \
<project_dir> <entry.ts> <window_fn> [args.json] [--timeout-s 300]
-
<entry.ts>puts one async function onwindowand imports the code under test with paths relative to<project_dir>:import { AudioSync, browserStreamAccess } from './src/player/audioSync' ;(window as any).runCheck = async (ref: unknown, url: string) => { let bytes = 0 // ...wrap the real thing, count what you need to measure... return { bytes } } -
args.jsonis a JSON array, spread into the call. -
stdout is one line: the function's return value as JSON. Console and page errors go to stderr.
-
Exit codes: 0 ok; 1 the function threw (or the page errored); 2 setup failed (no bundler, no Playwright, bundle error).
What it does, and the traps it already handles
| Step | Detail |
|---|---|
| Bundle | The project's own node_modules/.bin/rolldown, else esbuild, as an IIFE. Never npx to install one: a missing bundler is a setup failure to report. Runs with NODE_OPTIONS unset, which some repos set for other tools. |
| Imports | The entry is copied into <project_dir> as .live-check-entry-<pid>.ts (an entry outside the project could not resolve the project's modules). Removed on exit, always. |
| Serve | python3 -m http.server 0 on 127.0.0.1. The OS picks the port, so parallel runs and other worktrees never collide. |
| Browser | The project's own Playwright (playwright or @playwright/test), headless Chromium. |
| Teardown | A trap kills only the server PID this run started, and deletes the temp dir and entry copy. |
What ships with it
1 file 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.
- 17d ago First seen · 68 lines · 107 tokens per session scan A f211057adaf8
browser-live-check is a skill published in the GitHub repository chipi/agentic-ai-homelab (3 stars, last pushed today), licensed MIT. It adds 107 tokens to every session and 943 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-18.
Other skills, from other repositories
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
test-production
Runs bin/test-production.ps1 to acceptance-test a production (or prerelease) release of browser4-cli. Use when asked to run production tests, acceptance-test a release, or verify the published CLI.
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.
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
checking-a-page
Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Use after creating or editing an HTML page, or the JavaScript or CSS that a page loads.
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.