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 wahidyankf/ose-public --skill exploratory-testinggit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/exploratory-testing)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/exploratory-testing"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/exploratory-testing/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/wahidyankf/ose-public/exploratory-testing"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/exploratory-testing.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.00051 | $0.01314 |
| Opus 5.5 | $0.00020 | $0.00526 |
| Sonnet 5.5 | $0.00010 | $0.00263 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
exploratory-testing 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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploratory Testing
Exploratory and Usability Review owns the sequence: declared tasks, one bounded pass, and a terminal result. Enumerated Coverage and Usability Probes and Completeness own the sweeps that enumerate instead of sampling; Evidence Safety and Accessibility owns what a capture may hold; and API Testing owns the direct request an API change needs. This skill covers the tester's judgement inside that pass.
Frame Each Charter as a Mission
A charter names what to explore, with which resources or constraints, and what kind of information or risk it should reveal. For example: explore the discount field on checkout, with expired, stacked, and malformed codes, to reveal pricing and validation defects.
A charter as broad as "explore checkout" finds whatever lies on top. One that lists clicks is a script and cannot discover that a path was impossible to find. The workflow's declared tasks are these charters, frozen before the pass starts. Anything found outside a charter is still recorded, marked as outside it.
Vary the Angle With Tours
| Tour | Tends to find |
|---|---|
| the primary journeys, in varied order | defects in the flows people depend on |
| a record's lifecycle: create, change, store, show, remove | values altered or lost between steps |
| hostile input: invalid, boundary, oversized, out of order | validation and error-handling defects |
| one action repeated, quickly and many times | state and timing defects |
| the least-used settings and corners | paths nobody tested |
| the same view across viewport, locale, and theme | text and layout defects under change |
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.
- 2d ago First seen · 88 lines · 51 tokens per session scan A 5ae777f3775e
exploratory-testing is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,314 once invoked, about $0.0002 per session on Opus 5.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-10-14.
Other skills, from other repositories
ux-acceptance-coordinator
Coordinate black-box, agent-driven UX acceptance journeys against a disposable EmDash admin site. Use when preparing, dispatching, verifying, or reporting a manual browser journey performed by a separate tester agent. Do not use for deterministic Playwright tests or ordinary code review.
ux-acceptance-tester
Perform a goal-driven, black-box UX acceptance journey in a browser and report the path, friction, and observable outcome. Use only in an isolated tester context with a supplied start URL and brief.
playwright-page-objects
Use when creating page objects or refactoring Playwright E2E tests for better maintainability with Page Object Model patterns.
test-browser
Run browser tests on pages affected by current PR or branch.
playwright-praman-sap-testing
Package: playwright-praman Import: import { test, expect } from 'playwright-praman' Purpose: Primary instruction set for Praman AI agents (planner, generator, healer).
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.