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-cloud-investigate-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-cloud-investigate-test)<a href="https://agentmods.dev/skills/mamahoos/dot-files/k6-cloud-investigate-test"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/k6-cloud-investigate-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-cloud-investigate-test"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/k6-cloud-investigate-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.00215 | $0.03912 |
| Opus 5 | $0.00108 | $0.01956 |
| Sonnet 5 | $0.00043 | $0.00782 |
| Haiku 4.5 | $0.00021 | $0.00391 |
Grade A, and why
k6-cloud-investigate-test 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 5d 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.
This is a copy
98% identical to k6-cloud-investigate-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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
k6 Cloud test investigator
Structured 9-step workflow for investigating a Grafana Cloud k6 test or run.
This skill is workflow-only. All API calls go through gcx api against the plugin proxy, using v6 for REST and v5 for metrics. For the underlying mechanics (gcx auth, path conventions, endpoint discovery, log queries, script editing, threshold semantics, gotchas), see the k6-manage skill — every step below references it.
The content unique to this skill is:
- the ordered investigation flow (Steps 1-9 below)
- the date-alignment check ("last 7 days" ≠ "last 7 runs")
- the 3-layer pass/fail determination (
resultvsstatusvs per-checkchecksquery) - a worked example with realistic numbers (
references/worked-example.md)
Core principles
- Read before write. Always GET the script before any PUT.
gcx k6 load-tests update-scriptis a write that replaces the live script with whatever file you pass — running it "just to see the URL it hits" has cost users their production scripts. If you need to learn URLs, run any non-mutating command with-vvv --log-http-payloadinstead. - Paginate when enumerating runs. The
/test_runsendpoint caps at 1000 rows andgcx k6 runs list --limit 0does not auto-follow@nextLink. Use thegcx apiloop documented ink6-manage§3. - Verify date framing. When the user says "last 7 days", "this week", "recent runs" — confirm the most-recent run's
createdactually falls in that window. Surface the gap if not. check()doesn't fail runs; onlythresholdsdo. And thresholds with zero observations are reported as ✓ pass. See "Threshold semantics" below for the full deep dive; the per-checkchecksmetric query in Step 5 catches both cases.
Prerequisites
gcx installed and authenticated against the user's stack. See k6-manage §1. Verify with:
gcx --context <stack> config check # expect "✔ Connectivity: online"
Investigation workflow
Step 1: Identify the test and target run(s)
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.
- 5d ago First seen · 257 lines · 215 tokens per session scan A 39508b88b797
k6-cloud-investigate-test is a skill published in the GitHub repository mamahoos/dot-files (4 stars, last pushed today), licensed MIT. It adds 215 tokens to every session and 3,912 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to k6-cloud-investigate-test, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
wispr-flow-debug
Debug and test the Wispr Flow AutoHotkey dictation triggers (Copilot key + extra keys) from WSL by deploying macos.ahk to the Windows Desktop, reloading AutoHotkey, and reading the debug log. Use when an activation/trigger key isn't starting/stopping dictation, when the overlay clicks land wrong, or when verifying a…
speeding-up-laravel-tests
Use when Laravel/Pest test suites are slow, CI duration is growing, individual tests take seconds, or the user asks to speed up, optimize, or profile tests. Covers factories, fakes, config caching, XDebug/pcov, BCRYPTROUNDS, LazilyRefreshDatabase, and stray HTTP requests.
pytest
Python testing framework with powerful fixtures, parametrization, extensive plugin ecosystem, and support for async, Django, Flask testing.
playwright-visual-regression
Visual regression testing using Playwright with toHaveScreenshot(), masking, thresholds, cross-browser testing, and VUDA integration for AI-powered visual analysis.
django-tdd
Django testing strategies with pytest-django, TDD methodology, factoryboy, mocking, coverage, and testing Django REST Framework APIs.
django-verification
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.