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/rules/katalon-labs/true-skills/true-platform-testing)<a href="https://agentmods.dev/rules/katalon-labs/true-skills/true-platform-testing"><img src="https://agentmods.dev/badge/rules/katalon-labs/true-skills/true-platform-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/rules/katalon-labs/true-skills/true-platform-testing"><img src="https://agentmods.dev/badge/rules/katalon-labs/true-skills/true-platform-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.00192 | $0.10573 |
| Opus 5.5 | $0.00077 | $0.04229 |
| Sonnet 5.5 | $0.00038 | $0.02115 |
| Haiku 4.5 | $0.00019 | $0.01057 |
Grade A, and why
true-platform-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 18d 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 — 797 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katalon True Platform Testing
Use this skill for requirement-to-execution workflows in Katalon True Platform/TestOps, and as the router across the full 7-stage testing lifecycle. Prefer Katalon MCP tools for platform operations and Browser/Playwright only for external AUT exploration or visual verification.
Role Routing
Ask who is in front of you before asking which stage they are in. A skill is listed here when a request phrased in role terms, naming no skill, should land there first. Everything else is reached by handoff.
| Role | Comes here to | Starts at | Then |
|---|---|---|---|
| Manual tester | turn a written requirement into cases and run them | create-test-cases |
execute-test, analyze-failures |
| Automation tester | turn cases into code, run it, ship the results | test-case-to-playwright |
playwright-execute, upload-report, test-maintenance |
| Test lead | scope the cycle, judge readiness, keep the suite healthy | test-plan |
test-review, test-management, release-analyze |
| Test manager | read coverage and risk, and call ship | release-analyze |
test-review, test-management |
platform-setup is role-neutral and comes first for everyone who has not connected the MCP yet. Synonyms (SDET, automation engineer, QA engineer, QA analyst, test analyst, QA lead, QA manager), the full intent-to-skill map, and what to fall back to for the parts not built yet are in references/lifecycle-map.md.
Lifecycle Routing
The Katalon testing lifecycle has 7 stages. For a focused request, route to the matching skill; for a full-flow request, run the stages in order and stop when the user's goal is met. Full map + tool lists: references/lifecycle-map.md.
| Stage | Route to skill | When |
|---|---|---|
| 1 Plan | test-plan |
scope, risk-prioritized plan, executable folder+suite for a sprint/release |
| 2 Design | create-test-cases (+ test-case-to-playwright) |
author/import cases from requirements |
| 3 Manage | test-management |
organize inventory, classify, requirement traceability audit |
| 4 Review | test-review |
pre-pipeline coverage/quality/flakiness verdict |
| 5 Execute | execute-test (+ upload-report, playwright-execute) |
manual, Run with AI, automated, cloud |
| 6 Analyze | analyze-failures + release-analyze |
failure triage/defects; ship/no-ship call |
| 7 Maintain | test-maintenance |
repair flaky/broken cases, regenerate, feed gaps back to plan |
| pre / cross | platform-setup |
connect and verify the MCP |
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.
- 18d ago Changed · -28 tokens per session 279cc602bf36
- 1mo ago First seen · 797 lines · 220 tokens per session scan A 209b5796528e
true-platform-testing is a cursor rule published in the GitHub repository katalon-labs/true-skills (10 stars, last pushed yesterday), licensed MIT. It adds 192 tokens to every session and 10,573 once invoked, about $0.0008 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-08-31.
Other cursor rules, from other repositories
vibe-test
How to use the vibe-test MCP server for browser testing.
qa-engineer
Cursor rule "qa-engineer" from ulises-jeremias/agent-toolkit, covering qa engineer, responsibility, main skill domains, when invoked and delegate to skills.
e2e-runner
Cursor rule "e2e-runner" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, when invoked and selector priority (most to least resilient).
fusebase-flow-validation
Fusebase Flow validation/verification phase rules. Use when running gate checks, reviewing diffs, or verifying smoke prompts.
11-testing-standards
General testing and validation standards.
playwright
Playwright best practices for end-to-end testing with fixtures and page objects.