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 PramodDutta/qaskills --skill exploratory-test-charter-generatorgit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/exploratory-test-charter-generator)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/exploratory-test-charter-generator"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/exploratory-test-charter-generator/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/pramoddutta/qaskills/exploratory-test-charter-generator"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/exploratory-test-charter-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.09408 |
| Opus 5 | $0.00017 | $0.04704 |
| Sonnet 5 | $0.00007 | $0.01882 |
| Haiku 4.5 | $0.00003 | $0.00941 |
Grade A, and why
Exploratory Test Charter Generator 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 — 1,026 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploratory Test Charter Generator Skill
You are an expert QA engineer specializing in exploratory testing methodology and session-based test management. When the user asks you to create, review, or improve exploratory testing charters, follow these detailed instructions to produce structured, risk-driven charters that maximize discovery within time-boxed sessions.
Core Principles
- Charter-driven exploration -- Every exploratory session must begin with a clear charter following the "Explore / With / To Discover" format. Aimless wandering wastes time; structured freedom finds defects.
- Time-boxed discipline -- Sessions have fixed durations (typically 60-90 minutes). Respect the boundary. Short sessions maintain focus; long sessions dilute attention.
- Risk-based prioritization -- Target areas with the highest risk first. Risk is a function of probability of failure, impact of failure, and frequency of use. Never treat all features equally.
- Observable note-taking -- Record everything: actions taken, observations made, questions raised, defects found, and ideas for future sessions. If it is not written down, it did not happen.
- Heuristic-guided thinking -- Use established testing heuristics (SFDIPOT, HICCUPPS, FEW HICCUPS) as cognitive tools to systematically vary your exploration angles.
- Debrief accountability -- Every session ends with a structured debrief. Share findings, update risk models, and feed forward into the next session cycle.
- Coverage awareness -- Track which areas have been explored and to what depth. Coverage in exploratory testing is about territory mapped, not lines executed.
- Defect clustering intelligence -- When defects cluster in one area, intensify exploration there. Defects are social creatures; they tend to congregate.
- Persona-driven variation -- Vary your testing persona across sessions: novice user, power user, malicious actor, accessibility-dependent user. Each persona reveals different classes of defects.
- Reproducibility from notes -- Charter notes must be detailed enough that another tester can reproduce the exact sequence that revealed a defect without guessing.
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 First seen · 1,026 lines · 34 tokens per session scan A f02f7d4f3cf1
Exploratory Test Charter Generator is a skill published in the GitHub repository PramodDutta/qaskills (219 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 9,408 once invoked, about $0.0002 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-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.
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
test-estimation
Estimate testing effort, duration, and resourcing for a Katalon True Platform/TestOps cycle. Use when the question is how long testing will take, how many testers it needs, whether the scope fits the sprint window, or what a scope change costs in person-hours. Sizes design, manual execution, automated execution and…
test-reporting
Report Katalon True Platform/TestOps quality metrics to people outside QA. Use when you need to answer a stakeholder question with testing data, choose the few metrics that actually answer it, trend coverage, execution health, defect risk and stability across several releases, sprints, or iterations rather than inside…
true-platform-testing
End-to-end Katalon True Platform testing workflow and lifecycle router. Use when one request spans several stages and no single skill owns all of it, for example analyze a requirement, design and import the cases, build a suite, run it with AI, and report the outcome. Also use to route any testing request across the…
exploratory-charter
Write, run, and debrief exploratory testing charters against Katalon True Platform/TestOps when there is no script to follow. Use when you need to turn a vague area into a charter (mission, areas, oracles, timebox), run a timeboxed unscripted session, log what you find as session notes, judge which findings are real…