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/mamahoos/dot-files/k6-docsnpx skills add mamahoos/dot-files --skill k6-docsgit 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-docs)<a href="https://agentmods.dev/skills/mamahoos/dot-files/k6-docs"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/k6-docs.svg" alt="Measured on agentmods" 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 | $0.00150 | $0.00644 |
| Opus 5 | $0.00075 | $0.00322 |
| Sonnet 5 | $0.00030 | $0.00129 |
| Haiku 4.5 | $0.00015 | $0.00064 |
Grade A, and why
k6-docs 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 yesterday.
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.
This is a copy
98% identical to k6-docs — 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
k6 Documentation
Document or review k6 features across three repositories: k6-DefinitelyTyped (TypeScript types), k6-docs (user documentation), and k6 (release notes).
Workflow
Pick the workflow that matches the user's intent:
- Write documentation: follow references/workflows/write.md
- Review documentation: follow references/workflows/review.md
Quick References
- Repository structure & feature type identification
- TypeScript patterns & troubleshooting
- Testing workflow with parallel subagents
- agent-browser command reference
- Troubleshooting guide
Critical Rules
- Never push automatically - always ask first
- Never chain commands with
&∨- run each command separately (prevents failures) - Only document user-facing features - not internal implementation
- Use
1.for every numbered list item (not1.,2.,3.) - Test every code example against k6@master before committing
- No
Co-Authored-By: Claudeor AI attribution in commits
Validating examples (always run before committing)
Every code example in k6 documentation and release notes must execute cleanly against k6@master. The minimum loop:
# 1. cd into the k6 repo (not k6-docs or k6-DefinitelyTyped)
cd ~/path/to/k6
# 2. Make sure you're on master at the latest commit (the contract is k6@master)
git checkout master
git pull
# 3. Run each example as a separate command (no &&)
go run . run /path/to/script.js
If the run fails: read the error, fix the example in the source (doc or release note), re-run. Do not commit a change whose example doesn't run clean against current master. For the full multi-example workflow with parallel subagents, see references/testing-workflow.md.
What ships with it
20 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.
- references/agent-browser-reference.md 2.9 KB
- references/checklists/documentation.md 4.1 KB
- references/checklists/release-notes.md 783 B
- references/checklists/typescript.md 752 B
- references/repository-structure.md 3.9 KB
- references/subagent-prompts.md 3.4 KB
- references/templates/documentation.md 3.1 KB
- references/templates/release-notes.md 854 B
- references/testing-workflow.md 2.2 KB
- references/troubleshooting.md 4.7 KB
- references/typescript-patterns.md 4.2 KB
- references/workflows/review.md 2.7 KB
- references/workflows/write.md 5.4 KB
- scripts/check_agent_browser.sh 517 B runs code
- scripts/fetch_pr.sh 195 B runs code
- scripts/find_branch.sh 801 B runs code
- scripts/format_typescript.sh 236 B runs code
- scripts/test_typescript.sh 303 B runs code
- scripts/update_team_members.sh 1.4 KB runs code
- scripts/validate_links.sh 1.1 KB runs code
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.
- yesterday First seen · 53 lines · 150 tokens per session scan A 248bf0b6e518
k6-docs is a skill published in the GitHub repository mamahoos/dot-files (4 stars, last pushed today), licensed MIT. It adds 150 tokens to every session and 644 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to k6-docs, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
document-code
Apply Google Style documentation standards to Python, Go, TypeScript, and Terraform code. Use when writing or reviewing code that needs docstrings/comments/JSDoc, when asked to "document this code", "add docstrings", "follow Google Style", or when improving code documentation quality. Supports Python docstrings, Go…
openrct2
Develop plugins for OpenRCT2 - JavaScript/TypeScript scripting, game actions, UI windows, hooks, multiplayer sync.
vue-best-practices
MUST be used for Vue.js tasks. Strongly recommends Composition API with and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.
golang-style
Go conventions specific to this author. Use before writing or editing any Go (.go) file.
buildless-types
Use when the user asks to "set up types without a build step", "use vanilla JS with types", "configure erasable syntax", or mentions "JSDoc type checking". It provides instructions for modern type safety using JSDoc in browsers and native TypeScript execution in Node.js.
gsl-status
Query and configure the gsl (Go Status Line) that renders a powerline-style status bar in Claude Code and Antigravity CLI.