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/create-test-cases)<a href="https://agentmods.dev/commands/katalon-labs/true-skills/create-test-cases"><img src="https://agentmods.dev/badge/commands/katalon-labs/true-skills/create-test-cases/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/create-test-cases"><img src="https://agentmods.dev/badge/commands/katalon-labs/true-skills/create-test-cases.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.00130 | $0.03679 |
| Opus 5 | $0.00065 | $0.01840 |
| Sonnet 5 | $0.00026 | $0.00736 |
| Haiku 4.5 | $0.00013 | $0.00368 |
Grade A, and why
create-test-cases 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katalon Create Test Cases
Use this skill for the test design and import portion of Katalon True Platform work. Keep the larger true-platform-testing skill available as the end-to-end orchestrator; this skill is only the focused create/update/link workflow.
Availability Boundary
State the Katalon MCP boundary before promising writes:
- Available: list projects/repositories, find/read requirements, create/read/update/move test cases, find/manage folders, find/read/manage test suites, and link requirements to test cases.
- Not directly available: create requirements, create a formal Test Plan entity, inspect the live AUT UI, or guarantee downstream AI execution.
- Workaround for a test plan: create or reuse a named test suite/folder as the executable planning structure.
Read references/capability-boundaries.md when the user asks whether Katalon can do a specific operation.
Resolve Context First
Before mutating Katalon data:
- Call
list_projects. - Call
list_repositories. - Resolve the repository/Test Project from the user's wording, requirement key, or unique available repository.
Rules:
- Treat repository and Test Project as the same resolution target.
- If exactly one repository exists, use it.
- If multiple equally plausible repositories remain, ask the user to choose.
- If the user says "Katalon Cloud" or "cloud repo", prefer a repository named
Katalon Cloudwhen present. - Do not scan every repository just to avoid asking.
Analyze Requirement
If the user provides a requirement key, use find_requirements or read_requirement. If the user provides free text, analyze it locally and only link requirements when a real requirement ID is known.
Output or internally track:
- Requirement intent
- Personas
- Main flows
- Alternate and negative flows
- Data and environment assumptions
- Risk areas
- Coverage recommendations
Read references/requirement-analysis.md before analyzing non-trivial requirements.
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 · 320 lines · 130 tokens per session scan A 99f02d919616
create-test-cases is a command published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed 2d ago), licensed MIT. It adds 130 tokens to every session and 3,679 once invoked, about $0.0006 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.