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 tobihagemann/turbo --skill exploratory-testgit clone --depth 1 https://github.com/tobihagemann/turboWrote 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/tobihagemann/turbo/exploratory-test)<a href="https://agentmods.dev/skills/tobihagemann/turbo/exploratory-test"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/exploratory-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/tobihagemann/turbo/exploratory-test"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/exploratory-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 12 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00106 | $0.02457 |
| Opus 5 | $0.00053 | $0.01229 |
| Sonnet 5 | $0.00021 | $0.00491 |
| Haiku 4.5 | $0.00011 | $0.00246 |
Grade A, and why
exploratory-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploratory Test
Execute multi-level exploratory testing that goes beyond smoke testing to actively find bugs through escalating test scenarios.
Task Tracking
At the start, use TaskCreate to create a task for each step:
- Load or create test plan
- Determine testing approach
- Run
/user-experienceskill (when user-facing) - Execute tests by level
- Report
Step 1: Load or Create Test Plan
Resolve the test plan using these rules in order:
- Explicit path — If a file path was passed, use it
- Explicit slug — resolve to
.turbo/test-plans/<slug>.md - Anchoring artifact — If the work under test is anchored to a plan, resolve to
.turbo/test-plans/<that-slug>.mdwhen that file exists - Single file — Glob
.turbo/test-plans/*.md. If exactly one file exists, use it - Most recent — If multiple files exist, use the most recently modified
- Legacy fallback —
.turbo/test-plan.mdif.turbo/test-plans/does not exist - Nothing found — run the
/create-test-planskill first, then use the plan it writes
If multiple test plans exist and the most-recent choice is non-obvious, use AskUserQuestion to let the user pick from the candidates.
Read the resolved test plan and state its path.
Unless an explicit path or slug was passed, confirm the resolved plan still describes the work under test:
- Unavailable branch state — a scenario's steps require a branch that no longer resolves in the repository
- Completed prior run — every checkbox is already ticked and no recorded result is FAIL or PARTIAL
- Superseded context — the plan's Context section names work that changes merged since the plan was written have reversed or removed
When a signal fires, output the signal and the scenarios it affects as text. For a superseded Context, name the scenarios that exercise the reversed or removed work. Then use AskUserQuestion to offer:
- Regenerate — run the
/create-test-planskill with the resolved path, and use the plan it writes - Execute anyway — the signal is a false positive
- Pick another plan — resolve to a different test plan file, then confirm that plan against these same signals
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.
- 6d ago Changed · +4 lines 6e405b991eb4
- 10d ago First seen · 150 lines · 106 tokens per session scan A 75d00454551b
exploratory-test is a skill published in the GitHub repository tobihagemann/turbo (402 stars, last pushed yesterday), licensed MIT. It adds 106 tokens to every session and 2,457 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
offensive-fuzzing
Practical offensive fuzzing methodology covering target identification, fuzzer selection (AFL++, libFuzzer, Honggfuzz, Boofuzz, syzkaller), harness writing, corpus curation, mutation strategies, coverage measurement, and crash triage. Use when setting up or running fuzz campaigns against any target: file parsers…
offensive-business-logic
Business logic vulnerability testing for web/mobile/API engagements. Covers workflow bypass, state machine violations, multi-step process abuse, price/quantity/discount manipulation, currency confusion, coupon stacking, refund/chargeback abuse, race conditions on logic boundaries, parameter tampering for hidden flows…
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.
test-generator
A test-writing helper that creates unit or integration tests from the code's actual behavior and contracts. Unit tests check small pieces of code, while integration tests check how real components work together.
offensive-race-condition
Race condition (TOCTOU) testing checklist: identifying timing windows, Burp Suite Turbo Intruder, Last-Byte sync technique, rate limit bypass, double-spend attacks, and concurrent request exploitation. Use for web app race condition testing or bug bounty time-of-check-to-time-of-use bugs.