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.
git clone --depth 1 https://github.com/katalon-labs/true-skillsWrote 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/commands/katalon-labs/true-skills/exploratory-charter)<a href="https://agentmods.dev/commands/katalon-labs/true-skills/exploratory-charter"><img src="https://agentmods.dev/badge/commands/katalon-labs/true-skills/exploratory-charter/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/commands/katalon-labs/true-skills/exploratory-charter"><img src="https://agentmods.dev/badge/commands/katalon-labs/true-skills/exploratory-charter.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.00150 | $0.06142 |
| Opus 5 | $0.00075 | $0.03071 |
| Sonnet 5 | $0.00030 | $0.01228 |
| Haiku 4.5 | $0.00015 | $0.00614 |
Grade A, and why
exploratory-charter 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 yesterday.
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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katalon Exploratory Charter
Use this skill for the unscripted part of the design stage: a timeboxed session that learns something the written requirement does not say, then converts what it learned into scripted coverage. A charter is not a test case and a session is not a test run. The value is the learning plus the promotion, so a session that produces no notes and no promoted cases has failed even if nothing crashed.
Treat the human as a tool. Ask when the area, the timebox, the environment, or the risk appetite cannot be resolved safely. Never invent an oracle.
Availability Boundary
There is no exploratory session object in the platform. Say that before promising to "run a session in Katalon".
- Available via MCP: resolve scope (
list_projects,list_repositories), read the oracles you already have (find_requirements,read_requirement,fetch_requirement_data), check whether an area is already covered before spending the timebox on it (find_test_cases,find_test_cases_by_requirement), and land the outcome (manage_test_folder,create_test_case,link_requirements_to_test_case,manage_test_suite,read_test_suite). - Not available, and no workaround exists: a charter / session / session-sheet entity, a session timer or duration field, attachment upload for screenshots or video or HAR files, a tool that sets a manual test result to failed, custom fields or tags to mark a case as exploratory in origin, and creating a requirement for behavior the charter discovered. Do not reach for
create_charter,upload_attachment,set_test_result_status, ormanage_tags- none of them exists. - The defect trap.
create_defectrequires a known failed test result ID. An unscripted session produces no test result, so a charter finding cannot be filed through MCP as it stands. In order of preference: (1) file it in Jira or Azure DevOps directly, outside the MCP; (2) execute the reproduction case and mark it failed in the TestOps UI, then file from that run. A third path is MCP-legal but conditional - promote the finding to a case,create_manual_test_run,create_manual_ai_session, and if the AI run genuinely fails,create_defectwith that result ID. It only works when Run with AI actually reproduces the bug, so never offer it as the default. - The Katalon MCP cannot see the application. It reads and writes platform objects only. Every observation in a session comes from a browser you drive yourself, so use Browser or Playwright for the product and the MCP for the artifacts.
- Where the charter lives. Author the charter and the session sheet as a local artifact the user keeps. Optionally mirror the charter into the platform as one test case in the charter folder, mission in Description and session log in Steps. Say which you did.
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.
- yesterday First seen · 384 lines · 150 tokens per session scan A ad943e2e09ba
exploratory-charter is a command published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed 2d ago), licensed MIT. It adds 150 tokens to every session and 6,142 once invoked, about $0.0007 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-08.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
test-review
Act as a software quality engineer and python expert.
run_tests
Use the text the user typed after the command name as the request for this command.
write-unit-tests
Create comprehensive unit tests for the current code and generate the test file with proper imports and setup according to the project's testing conventions.
test
Command "test" from duongductrong/cursor-kit, covering purpose, analyze, test categories, output and rule.
implement_tests
Use the text the user typed after the command name as the request for this command.