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 k6git 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)<a href="https://agentmods.dev/skills/mamahoos/dot-files/k6"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/k6/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"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/k6.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.00199 | $0.03223 |
| Opus 5.5 | $0.00080 | $0.01289 |
| Sonnet 5.5 | $0.00040 | $0.00645 |
| Haiku 4.5 | $0.00020 | $0.00322 |
Grade A, and why
k6 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> **Agent-agnostic:** The steps below describe capabilities, not specific tools. Where a step says "fetch a URL" or "write a file", use whatever your agent provides for that capability (e.g. a web-fetch tool, a file-writ This is a copy
100% identical to k6 — 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
k6 Script Generation
Efficiency note: This is a short linear recipe (read example → adapt → save → validate → review). A todo list would just mirror the headings without adding value, so skip the planning overhead and execute the steps directly.
Agent-agnostic: The steps below describe capabilities, not specific tools. Where a step says "fetch a URL" or "write a file", use whatever your agent provides for that capability (e.g. a web-fetch tool, a file-write tool, or shell
curl/tee).
Step 1: Pick the right example file
Read only the file that matches the user's request. Examples provide structural scaffolding — the correct scaffold, option shapes, and import patterns.
| User needs | Read this file |
|---|---|
| HTTP REST, auth flow, batch requests | examples/http.js |
| HTML parsing with parseHTML, SharedArray | examples/html.js |
| WebSocket | examples/websocket.js |
| gRPC | examples/grpc.js |
| Browser automation | examples/browser.js |
Browser + functional test / expect() / k6-testing |
examples/functional.js (browser scenario) |
Functional/integration tests, expect(), k6-testing |
examples/functional.js |
| Custom metrics, execution module, handleSummary, per-vu-iterations | examples/metrics.js |
| Load patterns, all executors (ramping, arrival rate, per-VU, etc.) | examples/executors.js |
Cloud run, --local-execution, cloud options |
examples/cloud.js |
| Crypto (HMAC, MD5, SHA256) or encoding (base64) | examples/crypto-encoding.js |
| xk6-faker | examples/ext-faker.js |
| xk6-redis | examples/ext-redis.js |
| xk6-sql / sqlite3 / postgres | examples/ext-sql.js |
| xk6-exec | examples/ext-exec.js |
| xk6-dns | examples/ext-dns.js |
| xk6-tls | examples/ext-tls.js |
| xk6-tcp | examples/ext-tcp.js |
| xk6-crawler | examples/ext-crawler.js |
Example files live in the examples/ directory alongside this SKILL.md.
When the request matches multiple rows (e.g. "browser" + "functional test"), prefer the row whose assertion style fits the intent. If the user says "functional test", "assert", "verify", or "expect", use functional.js even if the test involves a browser — it demonstrates expect() with auto-retrying browser matchers. Use browser.js for browser load/performance tests that don't emphasize correctness assertions.
What ships with it
21 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.
- browser-best-practices.md 6.6 KB
- docs-guidance.md 2.6 KB
- examples/browser.js 3.5 KB runs code
- examples/cloud.js 2.1 KB runs code
- examples/crypto-encoding.js 2.6 KB runs code
- examples/executors.js 3.7 KB runs code
- examples/ext-crawler.js 1.1 KB runs code
- examples/ext-dns.js 1.3 KB runs code
- examples/ext-exec.js 1.0 KB runs code
- examples/ext-faker.js 1.3 KB runs code
- examples/ext-redis.js 1.8 KB runs code
- examples/ext-sql.js 2.1 KB runs code
- examples/ext-tcp.js 1.6 KB runs code
- examples/ext-tls.js 1.2 KB runs code
- examples/functional.js 3.5 KB runs code
- examples/grpc.js 2.4 KB runs code
- examples/html.js 2.1 KB runs code
- examples/http.js 3.6 KB runs code
- examples/metrics.js 3.8 KB runs code
- examples/websocket.js 1.9 KB runs code
- SETUP.md 1.4 KB
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 Changed · +2 lines · +27 tokens per session 15434c5b315d
- 1mo ago First seen · 193 lines · 172 tokens per session scan A 282d39fd88dc
k6 is a skill published in the GitHub repository mamahoos/dot-files (5 stars, last pushed today), licensed MIT. It adds 199 tokens to every session and 3,223 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to k6, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
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.
verify-ui-change-in-cloud
Verifies user-facing Warp client changes by spawning a cloud agent with computer use to test Warp. Use only when the user explicitly requested computer-use verification or accepted an offer to run it, and ONLY in non-sandboxed environments and local environments. Triggers a cloud agent that runs the test-warp-ui skill.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
enterprise-integration-testing
Use when testing enterprise integrations across SAP, middleware, WMS, or backend systems, validating E2E enterprise flows, testing SAP-specific patterns (RFC, BAPI, IDoc, OData, Fiori), or enforcing cross-system quality gates.