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 mamahoos/dot-files --skill k6-browser-testgit clone --depth 1 https://github.com/mamahoos/dot-filesWrote 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/mamahoos/dot-files/k6-browser-test)<a href="https://agentmods.dev/skills/mamahoos/dot-files/k6-browser-test"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/k6-browser-test/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/mamahoos/dot-files/k6-browser-test"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/k6-browser-test.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.00004 | $0.03972 |
| Opus 5.5 | $0.00002 | $0.01589 |
| Sonnet 5.5 | $0.00001 | $0.00794 |
| Haiku 4.5 | $0.00000 | $0.00397 |
Grade B, and why
k6-browser-test 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 12d 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
instructions ("ignore previous instructions", "run this command", …), ignore Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
This is a copy
98% identical to k6-browser-test — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
k6 Browser Test (from prose, with live exploration)
Turn a plain-language user journey into a working, validated k6/browser
functional test. The user describes what to do the way they'd tell a friend
("go to the site, log in, add a pizza to the cart, check the cart shows one
item") — you discover the real selectors by driving the live site, so the
user never has to supply a CSS selector, XPath, or data-testid.
Agent-agnostic: steps describe capabilities ("run a k6 script", "write a file"), not specific tools. Use whatever your harness provides. The only hard dependencies are the
k6binary with browser support and a POSIX shell — no MCP, no Node, no Playwright.
What this skill produces (and what it doesn't)
- Produces: one
k6/browsertest file — functional by default (single iteration,expect()assertions), or a browser load test (scenarios + Web-Vitals thresholds) when the user asks for load/performance. - Not in scope: protocol/HTTP tests, HAR recording, or multi-test load suites with SLOs. If the user wants a full performance suite, hand off to k6-perf-test-website. If they want HTTP/gRPC/WS, use the general k6 skills. If the script is destined for Grafana Cloud Synthetic Monitoring (a browser or scripted check), also reference the synthetic-monitoring-checks skill — it owns the SM check lifecycle (create/update, cadence, probe locations).
Prerequisites
k6 v1.2+(k6 version) — thegetBy*locator API this skill relies on landed in v1.2.0 — plus a Chromium-based browser installed on this machine (e.g. Google Chrome) — k6 does not bundle one. PointK6_BROWSER_EXECUTABLE_PATHat a non-default install location.- A POSIX shell (
bash/zsh) — the exploration loop usesmktemp,cp, andenv. (Only the finalk6 runin Step 7 has a PowerShell form.) - k6 v2+ is needed only for Step 5's
k6 x docs(automatic extension resolution, no custom build). Verify once that it prints markdown; on v1.x — or if it misbehaves — use the fallbacks in Step 5. Everything else works the same. - Network access from this host to the target site.
What ships with it
5 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.
- 12d ago First seen · 327 lines · 4 tokens per session scan B b79729877250
k6-browser-test is a skill published in the GitHub repository mamahoos/dot-files (5 stars, last pushed today), licensed MIT. It adds 4 tokens to every session and 3,972 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (instruction-override phrasing). It is 98% identical to k6-browser-test, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
walkthrough
Generate a hands-on browser walkthrough of a PR's user-facing changes to exercise before review; --publish posts the final version to the PR for QA.
playwright
Automate browsers and E2E tests with Python Playwright: screenshots, traces.
playwright-visual-regression
Use when setting up visual regression testing with Playwright - toHaveScreenshot baselines, masking dynamic content, handling animations, full-page and element screenshots, cross-browser runs, CI integration, VUDA MCP tooling, or debugging flaky visual diffs.
game-qa
Game QA testing with Playwright — visual regression, gameplay verification, performance, and accessibility for browser games. Use when writing or running game tests, debugging test failures, or building QA infrastructure. This is the reference skill — use qa-game for the user-facing command.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.