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 summarybotng/summarybot-ng --skill exploratory-testing-advancedgit clone --depth 1 https://github.com/summarybotng/summarybot-ngWrote 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/summarybotng/summarybot-ng/exploratory-testing-advanced)<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/exploratory-testing-advanced"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/exploratory-testing-advanced/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/summarybotng/summarybot-ng/exploratory-testing-advanced"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/exploratory-testing-advanced.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.00045 | $0.01647 |
| Opus 5.5 | $0.00018 | $0.00659 |
| Sonnet 5.5 | $0.00009 | $0.00329 |
| Haiku 4.5 | $0.00005 | $0.00165 |
Grade A, and why
exploratory-testing-advanced 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 1mo 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advanced Exploratory Testing
<default_to_action> When exploring software or investigating quality risks:
- CREATE charter with mission, scope, and time-box (45-90 min)
- APPLY heuristics: SFDIPOT (quality criteria), FEW HICCUPPS (consistency oracles)
- EXPLORE systematically using test tours (Business District, Bad Neighborhood, Historical)
- DOCUMENT findings in real-time with notes, screenshots, evidence
- DEBRIEF: What learned? What's next? Share via agent memory
Quick Heuristic Selection:
- What to test → SFDIPOT (Structure, Function, Data, Interfaces, Platform, Operations, Time)
- Recognize problems → FEW HICCUPPS (Familiar, Explainable, World, History, Image, Comparable, Claims, Users, Product, Purpose, Standards)
- Navigate app → Test Tours (12 types for different exploration strategies)
Critical Success Factors:
- Exploration is skilled, structured thinking - not random clicking
- Document discoveries, not pre-planned test cases
- Pair testing reveals more than solo exploration </default_to_action>
Quick Reference Card
When to Use
- Investigating new or changed features
- Finding bugs automation misses
- Learning unfamiliar systems
- Risk discovery before test planning
Session Structure (SBTM)
| Phase | Duration | Activity |
|---|---|---|
| Charter | 5 min | Define mission, scope, focus |
| Explore | 45-75 min | Systematic investigation |
| Note | Continuous | Document findings real-time |
| Debrief | 10-15 min | Summarize, prioritize, share |
SFDIPOT Heuristic (What to Test)
| Letter | Focus | Example Questions |
|---|---|---|
| Structure | Is it properly composed? | Code structure, UI layout, data schema |
| Function | Does it do what it should? | Core features work correctly |
| Data | Handles data correctly? | CRUD, validation, persistence |
| Interfaces | Interacts well? | APIs, UI, integrations |
| Platform | Works in environment? | Browsers, OS, devices |
| Operations | Can be used/managed? | Install, config, monitor |
| Time | Handles timing? | Concurrency, timeouts, scheduling |
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.
- 1mo ago First seen · 205 lines · 45 tokens per session scan A fed7cd725cbe
exploratory-testing-advanced is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 1,647 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-09-03.
Other skills, from other repositories
exploratory-testing-advanced
Advanced exploratory testing techniques with Session-Based Test Management (SBTM), RST heuristics, and test tours. Use when planning exploration sessions, investigating bugs, or discovering unknown quality risks.
context-driven-testing
Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Use when making testing decisions, questioning dogma, or adapting approaches to specific project needs.
Exploratory Test Charter Generator
Generate structured exploratory testing charters with focused missions, time-boxed sessions, risk-based areas, and standardized note-taking templates for systematic exploration.
api-testing-patterns
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.
contract-testing
Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing. Use when testing API contracts or coordinating distributed teams.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.